Evaluate PDFluent against your real workload. Every feature is unlocked. No watermarks. No artificial limits.
Unlicensed (no key needed)
Add the crate, run your code — no key required. Every feature works. Output PDFs carry a Producer metadata stamp marking them as unlicensed. Good for local testing.
Evaluation key (this form)
Request a signed 30-day evaluation key. The stamp is removed — output is clean and identical to a paid licence. No credit card. Delivered by email in under 2 minutes.
Fill in the form below. Your 30-day evaluation key is generated automatically and arrives by email in under 2 minutes.
+ 3 more features
Delivery: automated, usually in under 2 minutes.
Questions? [email protected] — we reply within 1 business day.
Add pdfluent to your dependencies. No system libraries, no C build steps — it compiles like any other Rust crate.
[dependencies] pdfluent = "1.0"
Your activation email walks through the exact steps for your channel. Activation mechanics evolve per binding during the public beta — see /docs/licensing for the current summary.
# See /docs/licensing for activation
The full API is available immediately. Load a PDF, parse an XFA form, render to image, convert to PDF/A — whatever you need to test.
let doc = Document::open("form.pdf")?;The evaluation is not a feature-limited demo. It is the full SDK with a time-limited licence key.
Replace the evaluation key with a paid licence key. Your code stays the same. Choose the plan that fits your team size — Lite, Plus, Professional, or Unlimited.
View pricingRemove the dependency from Cargo.toml. There is no subscription to cancel, no account to close, and no data stored on our end.
No. You receive an evaluation licence key by email. No payment details needed to start.
You may use it in a staging or pre-production environment to validate the SDK against your workload. For live production traffic, a paid licence is required.
After signing up, you receive a licence key by email with the activation steps for your chosen channel. Activation mechanics are evolving per binding during the public beta — the email is the canonical reference, and the plain-English summary lives at /docs/licensing.
After 30 days the licence key expires. The SDK will return an error until you add a valid paid licence key. Your code and build setup do not change — only the key needs to be replaced.