Foxit PDF SDK · Server & Backend

The Server PDF SDK Your Backend Embeds Without Sending Documents Anywhere

Your team ships rendering, generation, conversion, redaction, OCR and signing as features of your own product. The engine runs in-process on your servers, so documents stay inside your network and throughput scales with the infrastructure you already own.

Developer Documentation

PythonJavaC#C++Windows ServerLinuxmacOS32-bit64-bit

Trusted by 700M+ users and 640,000+ organizations worldwide

Operating Systems

Windows · Linux · macOS

Languages

Python · Java · C# · C++

Architecture

32-bit · 64-bit

Runtime

Headless · No GUI

Deployment

On-Premises · In-Process

Trial

30 days · full access

Choose Your Path

Start with the Backend You Already Run

Two of these are embedded libraries that run inside your own infrastructure. The third turns document content into structured data. Most teams start with one and add the other later.

Windows Server

Pick this if your backend is a .NET estate.

One SDK covers .NET Framework and .NET Core, which matters to teams running services on both mid-migration. Confirmed on Windows Server 2003, 2008, 2012 and 2016 in 32-bit and 64-bit builds, so adoption does not force an infrastructure upgrade first.

C# / .NET.NET CoreASP.NETJavaC++

See the Windows Server SDK

Linux

Pick this if you ship to cloud infrastructure or to hardware.

The same libraries serve scalable cloud applications and embedded Linux operating systems optimized for hardware products. RAM use stays low under intensive processing, and built-in out-of-memory recovery keeps a service running when a document pushes limits.

C++.NET CoreJavaPythonNode.jsGo

See the Linux SDK

Why Foxit Server SDK

What the Library Takes Off Your Roadmap

Backend PDF work usually stalls on three questions: where the data goes, what has to be installed alongside it, and who maintains the engine. Here is how each one resolves.

Data residency

Documents never leave your network

The SDK runs entirely within your own infrastructure. Processing happens on your servers, with no external API calls at runtime and no third-party upload step. That is the answer security review asks for in financial, healthcare, legal and government deployments.

No prerequisites

Nothing else to install on the box

Foxit's rendering engine is built in-house. There is no Microsoft Office install, no LibreOffice dependency and no open-source rendering library to license or maintain. Backend PDF processing runs cleanly on Linux or Windows without system-level prerequisites.

Proven engine

The engine behind the browsers you use

The open-source PDF engine inside Chrome and Edge was derived from Foxit's technology. The server SDK runs that same commercial engine, proven on billions of rendered documents, including the malformed files that break lesser libraries.

Headless

Built to run with no display layer

Foxit PDF SDK runs headless with no GUI dependency. Render pages to bitmap, generate documents, extract content and automate workflows entirely server-side.

Compliance

Controls your auditors already recognize

SOC 2 Type 2, HIPAA-ready, GDPR, TAA and Section 508. Native PDF encryption, permanent redaction at the data level, Microsoft RMS and IRM/DRM are all available server-side.

One API

One object model across the stack

Initialize with a license key, load a document, and reach rendering, forms, signatures, annotations and security through the same object model in every supported language.

Server libraries cover Python, Java, C# and C++, with Python available through pip as FoxitPDFSDKPython3. See the developer hub →

Core Server Capabilities

What Your Team Can Ship with It

Every capability below runs headless and in-process, on the servers you already operate.

Rendering

Headless page rendering

Render pages to PNG, JPEG or other raster formats for thumbnails, previews and document pipelines, using the same engine that drives desktop and mobile.

Explore

Forms

Programmatic form processing

Fill, flatten and extract data from AcroForms and XFA Forms server-side, so invoices, reports and compliance documents generate at volume with no user interaction.

Explore

Signatures

Server-side digital signatures

Apply, validate and certify signatures programmatically inside batch processing and approval pipelines.

Explore

Annotations

Server-side annotation processing

Create, edit, import and export annotations for review pipelines, automated redlining and pre-populated markup before delivery to end users.

Explore

Search & extraction

Full-text search and content extraction

SQLite-based full-text search and structured extraction index repositories and feed downstream systems with accurate document content at scale.

Explore

Security

Encryption, DRM and redaction

Apply native PDF encryption, integrate Microsoft RMS, and redact sensitive content at the data level rather than as a visual overlay.

Explore

Server-Side Use Cases

Backend Workflows Teams Build on It

Six patterns that come up most often in regulated and high-volume environments.

Web application PDF rendering

Render pages to images server-side and serve them over HTTP endpoints, powering browser-based viewers and preview generation from Flask, Django, Spring or ASP.NET.

Automated document generation

Fill AcroForms with data from your backend systems to produce personalized invoices, compliance certificates and client reports at scale.

Compliance redaction pipelines

Search for sensitive patterns across repositories, remove them permanently at the data level, and produce audit-ready versions with no operator step.

Digital signature automation

Sign and certify documents inside approval pipelines, with RMS and IRM integration enforcing access rights on the signed output.

Document repository indexing

Run full-text search and content extraction across large PDF repositories on your own infrastructure, feeding search indices and analytics.

OCR and archive preparation

Make scanned and image-only PDFs text-selectable at batch scale, ready for long-term storage and PDF/A-compliant preservation.

Supported environments

Operating systems: Windows · Linux · macOS, in 32-bit and 64-bit builds
Server languages: Python, Java, C# and C++
Runtime model: Headless, in-process, no GUI or display layer required
Dependencies: No Microsoft Office, no LibreOffice, no third-party rendering library
Network: No external API calls to Foxit services at runtime
Python install: pip install FoxitPDFSDKPython3, initialized with sn and key credentials

Windows Server (32/64-bit)Linux (32/64-bit)macOS (server)Flask / Django / FastAPISpring / Tomcat (Java)ASP.NET / .NET Core (C#)pip install (Python 3)

Add-Ons

Extend the Engine as the Workload Grows

These modules are available for server deployment alongside the core libraries.

Redaction

Search and permanently remove sensitive information at the data level, for GDPR, HIPAA and legal compliance in automated pipelines.

Explore

OCR Document Scanning

Server-side optical character recognition converts scanned and image-only documents into text-selectable, indexable PDFs at batch scale.

Explore

PDF/A Compliance

Create and validate PDF/A documents server-side, as required for long-term archival in legal, government and healthcare programs.

Explore

XFA Forms

Process, fill and extract data from complex XFA documents built for Adobe LiveCycle in headless backend workflows.

Explore

Digital Rights Management

Integrate Microsoft RMS and custom IRM/DRM to apply, enforce and audit document access rights across backend distribution.

Explore

Resources

Hand This Page to Your Developers

Everything a technical evaluator needs sits in Foxit's developer documentation.

Guide

Server-side integration guide

A working walkthrough for using Foxit PDF SDK inside a web application's server side, including initialization and page rendering.

Explore

API reference

C++ API reference

Classes, methods and examples for the core API that the server libraries share.

Explore

Documentation

Developer hub and samples

Sample projects and API references for every server language binding, with platform setup guides.

Explore

Windows platform guide →Linux platform guide →Documentation home →

Compliance

The same standards Foxit's enterprise customers audit against.

SOC 2 Type 2

HIPAA-Ready

GDPR Compliant

TAA Compliant

Section 508

On-Premises Deployment

No Runtime External Calls

See the Foxit Trust Center →

Frequently Asked Questions

Questions Buyers Ask About the Server SDK

What backend engineers, DevOps leads and IT architects raise most often during evaluation.

What languages does Foxit Server PDF SDK support?

Foxit PDF SDK supports Python, Java, C#, and C++ for server and backend development. Python support is confirmed with pip installation (FoxitPDFSDKPython3) and integration with Flask-based web applications. Java and C# support is available on both Windows and Linux server environments. C++ libraries are available in 32-bit and 64-bit builds for Linux and Windows.

Does the SDK require Microsoft Office to process documents?

No Microsoft Office install is required. Foxit's rendering engine is built entirely in-house and does not depend on Microsoft Office, LibreOffice, or any third-party rendering library. PDF processing runs on Linux servers or in containerized environments without installing Office software or managing its licensing.

Does document data leave my infrastructure when processing?

Documents stay inside your own network. Foxit Server SDK runs entirely within your own infrastructure, so all processing happens on your servers, with no external API calls to Foxit services at runtime, no third-party upload dependencies, and no documents leaving your network. This is a hard requirement for healthcare (HIPAA), financial, legal, and government deployments.

Can I run Foxit PDF SDK headless on a Linux server?

Yes. Foxit PDF SDK is designed to run headless with no GUI or display dependency. The server-side integration documentation confirms this with a working Python and Flask example that renders PDF pages to bitmap images and serves them over HTTP, entirely without a display layer. The same headless capability applies to Java, C#, and C++ on Linux.

What server-side PDF operations are supported?

Foxit Server SDK supports the full PDF lifecycle. That covers headless page rendering (PDF to bitmap or image), programmatic form fill and flattening (AcroForms and XFA), server-side digital signatures, annotation creation and export, full-text search and content extraction, encryption and decryption, permanent redaction, OCR (add-on), and PDF/A compliance validation (add-on). All operations run in-process on your server without external service calls.

How do I install Foxit PDF SDK for Python?

Install via pip in a Python virtual environment: pip install FoxitPDFSDKPython3. Then initialize the library with your license sn and key credentials, found in gsdk_sn.txt and gsdk_key.txt from your trial download. Foxit's server-side integration guide provides a complete working example using Flask that your team can use as a starting point for any Python web framework.

Is a free trial available for the server SDK?

Yes. Foxit offers a free 30-day trial with full SDK access for your chosen platform, including server environments. The trial includes the complete library, license credentials, documentation, and sample projects. Foxit's sales engineers are available during the trial to answer technical questions, help scope the integration, and build a licensing proposal for your backend infrastructure requirements.

Get Started

Ready to Embed Foxit PDF Processing in Your Backend?

Start a free 30-day trial with full server SDK access, or talk to a specialist who can answer technical questions, confirm platform compatibility, and build a licensing proposal for your backend infrastructure.