Questions, answered.
What developers and buyers ask about PDF-SDK — the platforms, licensing per app, trials, and what happens to your documents.
The SDK
iOS and iPadOS, Mac (through Mac Catalyst), Android, the web, Flutter and React Native. Every platform uses the same engine, so a document looks and behaves the same everywhere.
Yes. Users change the existing text itself — in any script, with its font, size and colour — and can move, rotate or restack it. It is not limited to adding new text boxes on top of the page.
With the tools your platform already uses: Swift Package Manager on Apple platforms, Gradle on Android, npm on the web and in React Native, and a plugin in Flutter. Set your key once at startup and open a document.
Yes. On iOS, Android, Flutter and React Native you choose the modes and tools, hide or rename menu items, set the colour scheme and add your own actions.
Yes. Every platform also has a document API, so your code can make the same kinds of edits the editor offers — for example reading and replacing text, adding text and images, or filling forms — and save the result.
Yes. Your app passes the password when it opens the document, or when it imports pages from one.
Licensing and trials
Per app: a key names the bundle IDs, package names or domains it covers. Choose a perpetual license with a period of updates, a subscription, or enterprise terms for site, wildcard and OEM use.
One product, identified by its domain on the web, its bundle identifier on Apple platforms and its package name on Android. Its debug variants, extensions and staging hosts can be included at no extra cost — or ask for a wildcard.
No. The Flutter plugin and the React Native package open the same native iOS and Android editor, so they use the same key: it lists your app’s bundle identifier and package name, whichever framework builds it.
Yes. A free 7-day trial unlocks every feature on every platform, in any app, with no watermark and no card — and the live demo runs the web editor in your browser.
No. PDF-SDK is commercial software; the trial key is for evaluation and expires. Without a valid key the editor does not open documents.
Never. There is no watermark and no reduced mode: with a valid key the SDK works fully, and without one the editor does not open documents.
Nothing changes for the apps you have: the key keeps working with every release published during your update period, forever. Renew only when you want releases published after it.
Talk to us. The standard SDK ships as compiled binaries.
Security and your data
No. PDF-SDK opens, edits and saves files inside your app or the browser tab. An online license check sends the license key, your app’s identifier and the SDK version — never document content or user data.
Yes. Standard license keys are checked on the device and need no network at all. Online licenses confirm with the license server from time to time and keep working offline in between — 30 days by default.
With a standard license key the SDK makes no network call at all. An online license asks the license server for a confirmation from time to time; the server keeps usage counts from those requests — never the document, the key or the IP address.
Not with a standard key: it is checked on the device and nothing is sent. An online license also confirms with our license server from time to time and works offline in between, 30 days by default.
On the device: the iOS Keychain (this device only), the Android Keystore, or a non-exportable Web Crypto key in the browser. You can also sign with your own HSM or signing service; the SDK never sees the private key.
Help and support
The documentation covers every platform, with an API reference for each. Integration questions come with your support plan; questions about licensing, pricing or a trial key go to sales.