Fast enough to be invisible
Rendering tuned for thin clients and mobile, so a 400-page file opens without a spinner your users will complain about.
Foxit technology ships inside products from
Two ways in
We Built the PDF Engine. You Choose Where It Runs.
Foxit APIs and SDK are built on the core we've maintained for two decades. The only question is whether document work belongs in your stack or in ours, and many platforms end up using both.
Foxit PDF SDK
Embed the same rendering and editing engine Foxit ships to Dell, Lenovo and Qualcomm directly in your app. Full control over UI, performance and where bytes live.
Foxit Document APIs
Call a REST endpoint and get the document back. Convert, merge, OCR, generate and sign at scale with nothing of your own to deploy, patch or capacity-plan.
Where documents are processed
Your servers, your clients, air-gapped networks. Nothing leaves your perimeter.
Foxit's cloud, with regional processing options and files purged after the job completes.
Platforms and languages
Web, Windows, macOS, Linux, iOS, Android
REST and webhooks, with client libraries for Node, Python, Java and .NET
What your team owns
Deployment, upgrades and the UI layer, with a prebuilt web viewer if you'd rather not draw one.
An API key and the calls you make. Capacity, patching and format edge cases are ours.
Time to first working prototype
Days. Integrate the library and a sample viewer.
Hours. Authenticate and post a file.
Works offline / air-gapped
Yes
No, requires outbound connectivity
Scaling model
You provision for peak
Elastic, billed on usage
Licensing basis
Per-developer plus redistribution, so your unit economics stay predictable as you scale.
Usage-based tiers with volume commitments, so a low-frequency feature costs almost nothing to launch.
Choose this when
Documents are core to your product, your customers demand data residency, or your app has to work offline.
You want to validate a feature fast, process in bursts, or keep document work off your roadmap entirely.
Foxit PDF SDK
Embed the same rendering and editing engine Foxit ships to Dell, Lenovo and Qualcomm directly in your app. Full control over UI, performance and where bytes live.
- Where documents are processed
- Your servers, your clients, air-gapped networks. Nothing leaves your perimeter.
- Platforms and languages
- Web, Windows, macOS, Linux, iOS, Android
- What your team owns
- Deployment, upgrades and the UI layer, with a prebuilt web viewer if you'd rather not draw one.
- Time to first working prototype
- Days. Integrate the library and a sample viewer.
- Works offline / air-gapped
- Yes
- Scaling model
- You provision for peak
- Licensing basis
- Per-developer plus redistribution, so your unit economics stay predictable as you scale.
- Choose this when
- Documents are core to your product, your customers demand data residency, or your app has to work offline.
Both start free
Foxit Document APIs
Call a REST endpoint and get the document back. Convert, merge, OCR, generate and sign at scale with nothing of your own to deploy, patch or capacity-plan.
- Where documents are processed
- Foxit's cloud, with regional processing options and files purged after the job completes.
- Platforms and languages
- REST and webhooks, with client libraries for Node, Python, Java and .NET
- What your team owns
- An API key and the calls you make. Capacity, patching and format edge cases are ours.
- Time to first working prototype
- Hours. Authenticate and post a file.
- Works offline / air-gapped
- No, requires outbound connectivity
- Scaling model
- Elastic, billed on usage
- Licensing basis
- Usage-based tiers with volume commitments, so a low-frequency feature costs almost nothing to launch.
- Choose this when
- You want to validate a feature fast, process in bursts, or keep document work off your roadmap entirely.
Both start free
Not mutually exclusive: plenty of platforms embed the SDK for the in-app viewer and call the APIs for batch conversion. One agreement covers both.
Capabilities
Deliver Document Experiences in Your Next Release
A real viewer inside your product
Users read, search, comment and mark up documents without downloading anything or leaving your app, including the file types your customers actually upload, not just clean PDFs.
Typically shipped as:SDKthe interaction has to feel native to your app
With the SDK
Drop in the prebuilt web viewer or build your own UI on the rendering API. Files stay on your infrastructure.
With the APIs
Render pages to images or HTML on demand when you only need read-only preview.
Why platforms pick Foxit
Leave the Document Code to the PDF Experts.
Foxit writes its own PDF core rather than reselling someone else's. That is why the same technology sits inside hardware from Dell, Lenovo and Qualcomm, and why format edge cases that break other libraries render correctly here.
Rated above Adobe Acrobat on quality of support and ease of setup across 1,000+ verified G2 reviews.
Passes your customer's security review
SOC 2, HIPAA and GDPR-aligned practices, a published advisory process, and on-prem options when the cloud is a non-starter.
Room to expand later
Start with viewing, add signing, generation, redaction or AI summarisation without onboarding another vendor.
Engineers on your integration
Solution engineers during evaluation, then a named technical contact once you are in production.
How to Get Started
Most platform teams have something working the same week they get a key.
1
Get a key
Self-serve trial for the SDK or the APIs. Full functionality, watermarked output, no time pressure.
2
Prototype the one flow that matters
Samples and a prebuilt viewer get a working slice in front of your PM before you commit engineering time.
3
Size the commercials
We model licensing against your deployment shape and volume, including redistribution and white-labelling.
4
Ship and grow
Go live with a named technical contact, then add capabilities as your customers ask for them.
Questions Platform Teams Ask
Yes. Foxit PDF SDK and Foxit Document APIs are covered by a single platform agreement and are commonly deployed together. A typical split puts Foxit PDF SDK behind the in-app viewer and editor, where latency and UI control matter, and Foxit Document APIs behind conversion and high-volume document generation. Combining both products does not require separate contracts or separate support paths.
Foxit platform licensing prices the right to embed Foxit technology in a software product and redistribute that technology to end customers. Seat licensing prices individual named users of Foxit's own applications, such as Foxit PDF Editor. Platform licensing is sized on deployment shape and volume rather than employee headcount. Foxit PDF SDK licensing is based on developer count plus redistribution. Foxit Document APIs licensing is usage-based with volume tiers.
Yes. Neither Foxit PDF SDK output nor Foxit Document APIs output is required to carry Foxit branding. The prebuilt web viewer, the editing interface, and the signing interface are themeable, so the document experience matches the host product's design system. White-labeling and redistribution rights are granted in the Foxit platform license agreement.
Files sent to Foxit Document APIs are processed for the requested job and then purged. Regional processing options are available where data residency is a requirement. Current certifications, retention terms, and security documentation are published in the Foxit Trust Center. Files processed with Foxit PDF SDK never leave the host environment, because Foxit PDF SDK runs entirely on customer-controlled infrastructure.
Foxit PDF SDK ships for Web, Windows, macOS, Linux, iOS, and Android. Foxit Document APIs are REST-based with client libraries for Node.js, Python, Java, and .NET, so any technology stack capable of an HTTPS request can call Foxit Document APIs. Individual Foxit PDF SDK add-on modules, including conversion and OCR, have narrower platform coverage. Per-module platform support is documented in the Foxit developer documentation.
Foxit platform partners are assigned a solution engineer during evaluation to validate the integration, then a named technical contact once the integration reaches production. Escalations route to the engineering team that maintains the Foxit PDF core rather than to a general support queue. Developer documentation, code samples, and API references are published at developers.foxit.com.
No. Foxit platform licensing sits alongside an existing Foxit channel or reseller agreement rather than replacing it. Platform licensing can be added to a current channel agreement, so embedding Foxit technology in a partner product and reselling Foxit licenses run under a single relationship.
Yes. Foxit maintains SOC 2, HIPAA, and GDPR-aligned practices, backed by a published security advisory process, plus on-premise deployment options for the SDK when the cloud isn't an option for your customers' data residency requirements.