Word to PDF on your own servers, with every page where it belongs
The OfficePDF on-prem SDK installs our own layout engine as a Windows service inside your network: no Office or LibreOffice, no phone-home. Table pagination, headers, footers and CJK typography follow Word's rules, and when correct output can't be guaranteed it refuses clearly instead of quietly shipping a wrong PDF.
- Runs fully offline
- License verified locally
- Per-server license, unlimited pages
- Python / Node.js / .NET / Java
Just want a quick look? Convert a document online — same engine in our cloud, for evaluating output only.
Why OfficePDF
Contracts, filings, reports, invoices — the layout is part of the content, and the documents often can't leave your network. OfficePDF handles both.
Fully offline, documents stay inside
Conversion, fonts and license checks all happen on your server. No online activation and no calls back to us, so it works on air-gapped networks too.
No Office, no LibreOffice
Runs as a standalone Windows service from a self-contained package — no Python install, no desktop session, no Office licensing. Tune concurrency to the hardware.
High fidelity
Font substitution, line height, paragraph spacing, tables across pages, floating objects and borders follow rules measured against Word, page by page.
CJK typography first
Punctuation compression, line-breaking rules, CJK/Latin spacing, vertical text and full-width characters are handled deliberately.
Strict mode, never silently wrong
In the default strict mode, content that can't be rendered correctly (such as unsupported equations) is rejected with a reason — not turned into a PDF that only looks fine.
Diagnostics for every conversion
Each report lists font substitutions, fallbacks and warnings with page numbers, so your system can decide automatically whether to accept the output.
Deploy to your Windows server in three steps
The on-prem service exposes exactly the same REST API as the cloud, so the official SDKs only need to point at the local address.
- 1
Install the service
Unpack the release and register it with officepdf-server install-service; it starts with Windows. It listens on 127.0.0.1 by default.
- 2
Drop in the license file
Put the .lic file in %PROGRAMDATA%\OfficePDF. It is verified locally with Ed25519 at startup — no online activation.
- 3
Call it from your system
One convert() call in the official SDK uploads, waits and downloads. To serve other machines, set an API key and open it to your network.
Requirements: 64-bit Windows Server. No Office, LibreOffice or Python needed. Linux is on the roadmap.
Read the deployment guide# Run as Administrator
# 1. License file: verified locally, no phone-home
$dir = "$env:ProgramData\OfficePDF"
New-Item -ItemType Directory -Force $dir | Out-Null
Copy-Item .\officepdf-lic_xxx.lic "$dir\officepdf.lic"
# 2. Install and start the service (127.0.0.1:8080)
officepdf-server install-service --port 8080
sc.exe start OfficePDFServer
# 3. Engine version, license expiry, queue depth
curl.exe http://localhost:8080/v1/health
# Serving other machines requires an API key:
# officepdf-server install-service --host 0.0.0.0 --api-key <secret>Samples use the on-prem service's default address, http://localhost:8080, with no key. Official SDKs: PyPI officepdf, npm @officepdf/sdk, NuGet OfficePDF.Sdk, Maven com.getofficepdf:officepdf-sdk.
See the evidence before you buy
Layout quality is best judged on real documents. All three options below run the same engine that ships in the on-prem SDK.
Page-by-page against Word
14 hard CJK and English documents: the PDF exported by Microsoft Word side by side with OfficePDF's output, with table breaks, headers, text boxes and more called out. Source files are downloadable.
View the comparisonConvert a few of your own
No sign-up: convert up to 5 documents a day online and see the real output and diagnostics. This runs in our cloud, so please don't upload confidential documents.
Try onlineValidate inside your network
Tell us about your documents and environment. We'll issue a time-limited evaluation license and the release package so you can batch-test real documents on your own servers.
Request an evaluation licenseOn-prem SDK first, cloud API when it fits
Both run the same engine behind the same API; your code differs by one base URL.
On-prem SDK
Runs on your own Windows servers
- Deployment
- Local install on Windows Server, fully offline capable
- Billing
- Annual license per server, unlimited pages
- Data handling
- Documents never leave your network
- Scaling
- Scale by licensed servers
- Updates
- All new versions during the license term
- Best for
- Air-gapped or regulated environments, high volume
Cloud API
Hosted option when you'd rather not run it
- Deployment
- Nothing to deploy — call over HTTPS
- Billing
- Prepaid page packs, charged per successful output page
- Data handling
- Files deleted after 7 days or on demand
- Scaling
- Managed scaling, up to 20 parallel jobs per account
- Updates
- Engine upgrades roll out automatically
- Best for
- Prototyping, low or spiky volume, no ops
Roadmap
Starting with Word, expanding to every Office format.
- .docxAvailable
Word 2007+ documents, with strict mode and full diagnostics.
- .docExperimental
Legacy Word 97-2003 files. Use preview mode and review the output.
- .xlsxPlanned
Excel to PDF with page breaks, print areas and scaling.
- .pptxPlanned
PowerPoint to PDF preserving layout, shapes and notes pages.
How do I evaluate the on-prem SDK?
On the contact page, choose "On-prem SDK / evaluation" and briefly describe your documents, server environment and expected volume. We'll issue a time-limited evaluation license and the release package — the same package as the paid version. You can also compare against Word on the showcase page, or convert a few non-confidential documents online first.
What does the server need?
A 64-bit Windows Server. No Office, LibreOffice or Python: unpack the release and run it, or register it as a Windows service. The service runs under a system account, so install the fonts your documents use "for all users". Linux is on the roadmap.
How is the on-prem SDK licensed?
The on-prem SDK uses a signed license file verified locally with an Ed25519 public key — no phone-home required. Licenses are per server per year with unlimited pages, and include all new versions during the term.
How does it compare to Office or LibreOffice?
We calibrate against Word's actual layout, with dedicated handling for the usual trouble spots — CJK typography, table pagination, headers and footers. No Office installation or licensing on your servers.
What's the difference between strict and preview mode?
Strict mode rejects a document whenever correct rendering can't be guaranteed, and tells you why — ideal for contracts and official documents. Preview mode always tries to produce output and flags fallbacks in the diagnostics report.
Which formats are supported?
.docx today, with experimental support for legacy .doc. Excel and PowerPoint are in development; existing customers will be the first to know.
Can I try the cloud API for free?
Yes. Verify your email and your cloud account gets 100 trial pages, usable on the web and through the API. No payment method required.
How is the cloud API billed? Am I charged for failures?
Successful output pages are deducted from your prepaid page packs. Rejected, failed and cancelled conversions are never billed. Page packs are valid for one year from purchase.
How long are files kept online and in the cloud API?
With the on-prem SDK, files only ever live on your own servers. In the cloud API, source files are deleted right after conversion; PDFs and reports are kept for 7 days for download and then purged automatically, and you can delete them at any time. Online try-it files are kept for an even shorter time.
Do you support invoices and bank transfer?
Yes. Pay by card in USD through Stripe, and Stripe emails your receipt. For bank transfer, a formal invoice or a purchase agreement, contact sales.
Validate it on your own servers
Tell us about your documents and environment. We'll issue an evaluation license and help you test with real business documents.