# iOS Battery Health and Performance Tips Ways to extend iPhone battery life and troubleshoot issues. - **Source:** [r/iPhone](https://brifing.si/source/65bd5ccb-b1f4-4747-91e7-cf5959dd2097) - **Published:** 2026-07-10 - **Topic:** [Software & Engineering](https://brifing.si/c/engineering) - **Original article:** - **On Brifing:** https://brifing.si/s/ddb1a966-b32a-47f2-b138-64ea0985f024 ## What is Battery Health? iPhone battery health varies depending on usage and various factors. A decline of 7-10% per year is considered normal. After two years, battery health typically ranges between 80-85%. This is not a cause for concern. ## When is Battery Replacement Needed? Apple recommends battery replacement when battery health falls below 80% and there is a noticeable decrease in battery life. If this happens within the first year, you may be eligible for a free battery replacement. Out of warranty, the cost ranges between $69-$89. ## Battery Life Issues Battery life issues can be categorized into three types: Normal decline due to usage, problems caused by updates or iOS bugs, and abnormalities due to battery aging. These issues can affect device performance. ## Troubleshooting Battery Problems If you experience battery issues, first check your battery health. If it’s below 80% or you suspect age-related problems, contact Apple Support. For new or updated devices, wait for background processes to complete. ## Tips to Extend Battery Life To extend battery life, use low power mode, disable background app refresh, enable auto-lock, and manually adjust brightness. For OLED devices, prefer dark mode. ## Preserving Battery Lifespan To preserve battery lifespan, avoid extreme temperatures, remove the case while charging, and store the device in a cool place at half charge if unused for long periods. Charge it every six months during storage. ## Sources covering this story - https://www.reddit.com/r/iphone/comments/1usl08g/weekly_ios_battery_support_megathread/ — --- _Summary written by Brifing from the original reporting. Copyright in the original article belongs to its publisher; read the full piece at the link above._