Skip to content

PDF-SDK 2.4.1 is out.See what’s new

PDF-SDK
Skip to Content
Docs

System requirements

The minimum OS, toolchain and devices for PDF-SDK on iOS, iPadOS, Mac Catalyst, Android, the web, Flutter and React Native.

Every platform ships the same release, so these are the minimums for PDF-SDK 2.4.

At a glance

PlatformMinimumToolchainDevicesNotes
iOS and iPadOSiOS 15Swift 6; built and tested with Xcode 27iPhone, iPad, simulatorsSwift Package Manager
Mac CatalystMac Catalyst 15Xcode 27Apple silicon and IntelThe Form Editor mode is not available
AndroidAPI 26 (Android 8.0)Gradle, Maven dependencyarm64-v8a16 KB page-size compatible
WebWebAssembly threads, WebGL2, SharedArrayBuffernpm package and the wasm/ folderDesktop and phone browsersServed over HTTPS, cross-origin isolated
FlutterFlutter 3.44 (tested on 3.47)Swift Package Manager enablediOS 15+, Android API 26+ (arm64-v8a)No CocoaPods
React NativeReact Native 0.87Swift Package Manager setupiOS 15+, Android API 26+ (arm64-v8a)No CocoaPods

iOS 14 and earlier. PDF-SDK 2.0 moved the minimum to iOS 15, because Xcode 27 builds nothing lower. To ship to iOS 14, stay on Xcode 26 and PDF-SDK 1.14.3. See the 2.0.0 release notes.

Web browsers

The web editor needs WebAssembly threads, WebGL2 and SharedArrayBuffer, which browsers allow only on a page that is cross-origin isolated — served over HTTPS (or localhost) with the Cross-Origin-Opener-Policy and Cross-Origin-Embedder-Policy headers. See Serve it cross-origin isolated.

The automated test suites run in current Chrome at desktop and phone sizes, and Safari is used in development. Other browsers with those features should work, but are not part of the test matrix.

Android devices

The SDK ships for arm64-v8a. On a device without it, PdfEditorSdk.isSupportedDevice is false — check it before you open the editor. See Troubleshooting.

A license key

Every platform needs a license key for your app's bundle identifier, package name or web domain, set once at launch. See License keys.