JPedal
Pure Java PDF library for rendering, extraction, viewing and manipulation, with published prices.
Operated by IDRsolutions
Where your files are processed
No server involved
A Java library that runs in your own JVM, on-premise or in your own cloud. IDRsolutions operates no document processing service; the vendor's own framing is that it runs in the same JVM with no native process bridge. That is a property of the library itself: what an application built with it does with your file depends on that application, not on this.
It is an embedded Java library, so it runs inside the application that includes it, on whatever infrastructure that application runs on, which can include a server. That is not the same as a server-free deployment, and it is not a statement about the host application’s network behaviour.
What it does
JPedal is a Java PDF library with no native dependencies: one jar, no JNI, runs on any JVM from Java 17. It renders pages to images, extracts text and images, includes an embedded Swing viewer, and handles manipulation, digital signing, forms including XFA, annotations and inspection. It is sold with a one-off server or OEM licence and optional annual support, and the vendor publishes its prices rather than requiring a sales conversation — which in this index is nearly unique among commercial PDF SDKs.
Best for: Java teams that need PDF handling inside the JVM without shelling out to a native tool, particularly where an embedded viewer matters — the vendor's own comparison notes that neither PDFBox nor iText ships one. The absence of native dependencies is the other reason teams pick it: one jar means no version mismatches and no separate process to babysit.
Worth knowing: Its redaction entry is a word in a feature list rather than a described mechanism, so this index records the verdict as unverified — a reader who needs redaction should check what the API actually does to the file before relying on it. The licence is commercial, and while the pricing is published, the model is a one-off server or OEM fee with support billed annually after the first year, which is a different cash profile from a subscription and worth modelling before comparing it with one. The comparison material on the vendor's own site is unusually direct about competitors — it names iText's AGPL obligation and PDFBox's lack of a viewer and of commercial support — and it is marketing written by a party with an interest in the outcome, however accurate the individual statements are. Being pure Java with no native code is a real benefit and also a limit, but the limit is not rendering fidelity: language architecture does not establish how well a renderer reproduces a page, so anything needing a browser-grade renderer is a question about output rather than a scope boundary to declare.
Details, and where each comes from
Vendor statements, our own reading of their pages, and the things nobody has established yet, each answered separately. Where we have not confirmed something it says so rather than guessing, and a row nobody has established is greyed out.
- Versions covered
- Self-hosted
- Website
- idrsolutions.com
- Requires an account
- Not applicable
- Free tier
- No
- Watermark on trial output
- Not verified
- Maximum file size
- Not verified
- Batch processing
- Yes
- Data residency
- Self-hosted
- Open source
- No
- Self-hostable
- Yes
- Licence
- Commercial: one-off server or OEM licence, with optional annual support and maintenance after 12 months
- Redaction
- Not determined
- Programmatic access
- Embeddable library
- Last availability check
- Responded in 424 ms 16 October 2026
Checked automatically by our own runner, not reported by the vendor. 100% of our last 30 checks got a response.
Why we have not determined this
“PDF rendering to image, embedded PDF viewer, text extraction and search, PDF manipulation, digital signing, redaction, form handling (AcroForms and XFA), annotations, and PDF inspection.”
What that does not establish: RECORDED AS UNVERIFIED, and it is the third record in this campaign where a redaction feature exists but the mechanism is undocumented. The word appears once, in that list, and nowhere on the page is it explained: nothing says whether content is removed from the page or covered, and there is no redaction-specific page to read — the site's navigation offers converters, viewer pages and a buyer's guide but nothing about redaction. It is not `none`, because the feature is claimed to exist. What would settle it: the API documentation for the redaction call, or a canary test during the trial, which the vendor explicitly invites.
What the vendor says
Claims are labelled rather than repeated as fact. Where we have checked something ourselves, it says so and shows when. Checked means we read the vendor's own page and it says what we recorded — not that we tested the behaviour, unless the note says we did.
-
“JPedal is a pure Java PDF library — no native binaries, no third-party dependencies, no JNI. Runs on any JVM, on-premise or in the cloud, Java 17+. It gives you a single, well-documented Java PDF API for rendering, extraction, viewing, and manipulation.”
Checked by us — the source says this Read 1 October 2026
Confirmed. The quoted text appears in the rendered page as read on 2026-10-01. This claim was carried as reported rather than checked until this read.
Standing: Not re-read against the live source
Check it yourself: the source, the SHA-256, and how we checked
- From
- the text a browser renders
- SHA-256
- 48e0f3e510e4c7968cb5eb577545adb0675015a7d144a755fa3ebf62b223942d
How we checked: Read as rendered text in headless Chrome on 2026-10-01 and saved to the evidence archive, so the read can be repeated against the same file. Comparison ignores case, punctuation and hyphenation, which is why "open-source" on the record matches "open source" on the page.
-
“JPedal offers a simple, one-off server or OEM licensing model for customers with an optional recurring annual support/maintenance fee after 12 months. Prices are on the website and there are no sales calls required to find out what it costs.”
Checked by us — the source says this Read 1 October 2026
Confirmed. The quoted text appears in the rendered page as read on 2026-10-01. This claim was carried as reported rather than checked until this read.
Standing: Not re-read against the live source
Check it yourself: the source, the SHA-256, and how we checked
- From
- the text a browser renders
- SHA-256
- 48e0f3e510e4c7968cb5eb577545adb0675015a7d144a755fa3ebf62b223942d
How we checked: Read as rendered text in headless Chrome on 2026-10-01 and saved to the evidence archive, so the read can be repeated against the same file. Comparison ignores case, punctuation and hyphenation, which is why "open-source" on the record matches "open source" on the page.
Each claim is quoted from the vendor's own pages. This section describes what we have and have not checked — it is not a judgement about anyone.
Sponsorship is distribution, not an endorsement or a promise of search rankings, AI citations, traffic, or sales. This listing is a free entry, compiled from published sources.
Related reading
- Which PDF tools keep your file on your machine — what we count as processing on your own device.