Minimum iOS Version in 2026: How to Pick a Minimum iOS Target
In 2026 most new apps set the minimum iOS version to iOS 16 or 17. Take the highest of Apple's adoption data, your user data and your API needs.
The right minimum iOS version for a new app in 2026 is iOS 16 or iOS 17. Keep iOS 15 only if a meaningful share of your users still have older devices, and don’t consider anything earlier. To decide, check three things in order: Apple’s published OS share, your own app’s user data, and the minimum versions required by the APIs and libraries your core features use, then take the highest of the three. Below are the oldest devices each iOS version supports and popular framework requirements, with Apple’s rules as of October 2026.
What share of devices runs each iOS version?
Apple publishes OS share on its App Store usage page, counting devices that made App Store transactions on a given day. As of October 2026, the latest count on the page is from June 7, 2026.
| Devices counted | Share on the latest major version |
|---|---|
| All iPhones | 79% on iOS 26 |
| iPhones introduced in the last four years | 86% on iOS 26 |
| All iPads | 68% on iPadOS 26 |
| iPads introduced in the last four years | 79% on iPadOS 26 |
These numbers only tell you how much of the base is on the latest version. The remaining 21% is spread across iOS 18 and earlier, and Apple doesn’t break it down by version. Part of that 21% is devices like the iPhone XS and XR that can’t install iOS 26, as the table in the next section shows.
Keep two things in mind when you use this data. It counts active App Store devices worldwide, and your audience may skew older (for example apps for seniors, price-sensitive markets or company-issued older devices) or newer (for example apps for developers or photography enthusiasts). Also, iOS 27 shipped in September 2026, so the next update will report the iOS 27 share.
How do you use your own data to set the minimum iOS version?
If your app is already live, your own data beats any global statistic.
- Analytics or crash reporting SDKs. Most analytics and crash reporting tools can group by OS version. Look at the active user distribution for the last 30 days.
- Server logs. Have the app send the OS version in the User-Agent or a request header, then count unique daily active users per version.
- Weight by revenue. Paying and free users may have different devices. If iOS 15 users are 3% of your base but bring in almost no subscription revenue, dropping them costs little.
A common rule of thumb is that once all active users on a version and below add up to less than 2% to 5%, you can consider dropping it in your next major release. For a new app that hasn’t launched, use Apple’s numbers from the previous section.
Which iOS version do common APIs require?
If your deployment target is lower than the version that introduced an API, the compiler reports is only available in iOS 17.0 or newer. You then have to wrap it in if #available and write a fallback or hide the feature on older systems. The table lists the minimum versions of common features, taken from the availability annotations in the iOS SDK.
| Feature | Framework | Minimum iOS |
|---|---|---|
| New in-app purchase API | StoreKit 2 | 15 |
| Swift Charts | Charts | 16 |
| Shortcuts and Siri actions | App Intents | 16 |
| Live Activities and the Dynamic Island | ActivityKit | 16.1 |
| Local database | SwiftData | 17 |
| Interactive widget buttons | SwiftUI Button(intent:) |
17 |
| Feature tips | TipKit | 17 |
| On-device large language model | Foundation Models | 26 |
For a more detailed table of SwiftUI features by version, see SwiftUI or UIKit. If a new capability such as Live Activities or SwiftData is your app’s main selling point, set the minimum to the version it needs. That’s much simpler than adding checks at every call site.
For features that aren’t core, keep the lower minimum and turn the feature on only on newer systems.
1import SwiftUI
2import TipKit
3
4@available(iOS 17.0, *)
5struct NotificationTip: Tip {
6 var title: Text { Text("Turn on notifications") }
7 var message: Text? { Text("Get notified as soon as an item is back in stock") }
8}
9
10struct SettingsView: View {
11 var body: some View {
12 List {
13 if #available(iOS 17.0, *) {
14 TipView(NotificationTip())
15 }
16 Toggle("Restock alerts", isOn: .constant(true))
17 }
18 }
19}
20
21func configureTips() {
22 if #available(iOS 17.0, *) {
23 try? Tips.configure()
24 }
25}
This code compiles with a deployment target of iOS 15 in both the Swift 5 and Swift 6 language modes. Users on iOS 15 and 16 don’t see the tip, and everything else works the same.
What’s the oldest iPhone each iOS version supports?
Whatever version you choose as the minimum, you give up the devices that can’t install it. The table comes from Apple’s official lists of compatible iPhone models.
| iOS version | Oldest supported iPhones | Dropped compared with the previous version |
|---|---|---|
| iOS 15 | iPhone 6s, 6s Plus, iPhone SE (1st generation) | Same as iOS 14 |
| iOS 16 | iPhone 8, 8 Plus, iPhone X, iPhone SE (2nd generation) | iPhone 6s, 7 series, SE (1st generation) |
| iOS 17 | iPhone XR, XS, XS Max | iPhone 8, 8 Plus, iPhone X |
| iOS 18 | iPhone XR, XS, XS Max | Same as iOS 17 |
| iOS 26 | iPhone 11 series, iPhone SE (2nd generation) | iPhone XR, XS, XS Max |
| iOS 27 | iPhone 11 series, iPhone SE (2nd generation) | Same as iOS 26 |
Sources are the supported models pages in the iPhone User Guide for iOS 15, iOS 16, iOS 17 and iOS 18, and the compatible devices list on the iOS 27 page. iOS 18 and iOS 27 didn’t drop any iPhones, so iOS 17 and iOS 18 cover the same devices, and so do iOS 26 and iOS 27.
That shows where the trade-off sits. With a minimum of iOS 17 or iOS 18 you still reach the 2018 iPhone XR and XS. With iOS 26, those three models can’t install your app.
What minimum iOS version does Apple require for uploads?
Apple’s rules also constrain your minimum version. As of October 2026, Upcoming requirements lists two version-related rules.
| Requirement | Effective date | Details |
|---|---|---|
| Minimum SDK | April 28, 2026 | Uploaded apps must be built with Xcode 26 or later and the iOS 26 SDK |
| Minimum deployment target | September 9, 2026 | Uploaded iOS and iPadOS apps must have a deployment target of iOS 13 or later |
iOS 13 is only the floor for uploads. Apple’s Xcode support page states that Xcode 26 and Xcode 27 both support deployment targets from iOS 15 for upload. So in practice the lowest version you can choose is iOS 15.
The SDK version and the deployment target are different things. The SDK decides which APIs you can call, and the deployment target decides which systems the app installs on. Building with the iOS 27 SDK and a deployment target of iOS 16 is a normal combination.
What do Flutter, React Native and Expo require?
When you use a cross-platform framework or a large third-party SDK, your minimum can’t be lower than theirs. As of October 2026, their official docs state these versions.
| Framework / SDK | Version | Minimum iOS | Source |
|---|---|---|---|
| Flutter | 3.47 | 15 | Supported deployment platforms |
| React Native | 0.76 and later | 15.1 | React Native community announcement |
| Expo | SDK 56, 57, 58 | 16.4 | Expo SDK versions |
| Firebase Apple SDK | 13.0.0 | 15 | Firebase iOS release notes |
These are the frameworks’ own requirements. The plugins and pods you use may need more. Your final minimum is the highest version any dependency requires. For pod install failures caused by a Flutter plugin raising the version, see Common Flutter iOS build errors. If you use Expo, your minimum is at least 16.4.
Does raising the minimum iOS version affect existing users?
If you raise the minimum from iOS 15 to iOS 17, the new version you submit only installs on iOS 17 and later. For users on systems older than iOS 17, here’s what happens.
- The version they already have keeps working. The app isn’t deleted or disabled.
- They stop getting updates. New features and fixes you ship won’t reach them.
- New users may not be able to install it. On older systems the App Store sometimes offers the last compatible version, mostly for Apple Accounts that downloaded the app before. Apple doesn’t formally promise developers this behavior, so don’t treat it as a compatibility plan.
- Your server has to support old versions. Older app versions keep calling your API. Before you change fields or retire old endpoints, check how many users are still on old versions, or show an upgrade prompt in the old version.
Before raising the minimum, do three things.
- Use your analytics to work out the share of users affected.
- Fix known serious bugs in the last version that supports the old systems, because it will live on those devices for a long time.
- Tell users in the app or in the release notes which OS version the new release needs.
How do you change the deployment target in KXBuild?
When you use KXBuild on Windows, Linux or macOS, right-click the target in the KXBuild view, choose KXBuild: Edit Target Settings, change iOS Deployment Target in the Deployment Info section of the General page, and press Ctrl+S to save. It maps to the IPHONEOS_DEPLOYMENT_TARGET build setting. See Project settings. The built-in templates target iOS 15. See Built-in templates.
You can also change it from the command line.
1kxbuild project add-setting -k IPHONEOS_DEPLOYMENT_TARGET -v 16.0 -t MyApp -P .\MyApp.xcodeproj
If the project uses CocoaPods, set platform :ios in the Podfile to the same value and run pod install again. When the two don’t match, dependencies may be compiled for the old version. Rebuild once afterwards, and the compiler checks every API call that needs more than your new minimum iOS version.
FAQ
What minimum iOS version should a new app support in 2026?
Usually iOS 16 or iOS 17. According to Apple’s count from June 7, 2026, 79% of iPhones are on iOS 26, and a minimum of iOS 17 still covers the iPhone XR and XS. With Expo the minimum is at least 16.4, and with SwiftData it’s at least 17.
What’s the minimum deployment target Apple requires?
As of October 2026, iOS apps uploaded since September 9, 2026 must have a deployment target of iOS 13 or later. Xcode 26 and 27 support deployment targets from iOS 15, so in practice the lowest version you can choose is iOS 15.
Can users on older systems still use my app after I raise the minimum version?
Yes. The version they already installed isn’t deleted, they just stop getting updates. New users on older systems may not be able to install it. The App Store sometimes offers the last compatible version, but Apple doesn’t promise developers this behavior.
Which iPhones support iOS 27?
According to Apple’s compatibility list, iOS 27 supports the iPhone 11 series, iPhone SE (2nd generation) and later, the same as iOS 26. The iPhone XR, XS and XS Max top out at iOS 18.
What’s the difference between the deployment target and the SDK version?
The SDK version decides which APIs you can call at build time, and Apple requires the iOS 26 SDK or later. The deployment target decides the lowest OS version the app installs on, and it can be much lower than the SDK, for example building with the iOS 27 SDK and a deployment target of iOS 16.