Pyntra
Craft PDFs in any browser, with any UI library
Beta · v1.0.0 · MIT licensed
Craft PDFs in any browser, with any UI library
Client-side PDF editor with React headless hooks and a bring-your-own UI adapter. Fill and add form fields, sign and stamp, annotate, redact, and edit encrypted PDFs — all entirely in the browser with zero third-party PDF dependencies.
Key capabilities
- Form filling — text, multiline, date, number, checkbox, radio, dropdown, listbox
- Add new fields via drag-to-draw rectangle interface
- Sign & stamp with signature pad and image embedding
- Annotate — highlight, draw, eraser, redact, crop, shapes
- Encrypted PDF support — RC4, AES-128, AES-256
- Bring-your-own UI — Material UI, Tekivex UI, or custom adapter
Resources & quick links
What is Pyntra?
Pyntra is a browser-native PDF editor delivered as React headless hooks. Every operation — filling form fields, adding new fields, signing, stamping, annotating, redacting, and editing encrypted documents — happens entirely client-side. The PDF never leaves the browser, which matters for documents containing personal or regulated data.
It ships with zero third-party PDF dependencies and a bring-your-own-UI model: Pyntra owns the document logic and exposes it through hooks, while you render the interface with Material UI, Tekivex UI, or your own components. That separation lets you match your product's look exactly instead of fighting a pre-styled viewer.
How it works
- Load in the browser. A PDF is read into memory client-side. Pyntra parses the document structure — pages, form fields, annotations, and encryption — without a server round-trip.
- Edit through hooks. React hooks expose the document state: field values, annotation layers, signatures, and redactions. Your UI calls these hooks; Pyntra keeps the underlying PDF consistent.
- Export securely. On save, Pyntra serialises the edited document back to a PDF, optionally re-encrypting with RC4, AES-128, or AES-256 — all in the browser, so sensitive content is never uploaded.
When to use Pyntra
- Healthcare, legal, and finance apps where uploading documents to a server is a compliance risk.
- Form-filling workflows — text, date, number, checkbox, radio, dropdown, and listbox fields.
- Signature and stamping flows with a signature pad and embedded images.
- Redaction of sensitive content before sharing, performed entirely on the client.
Limitations & honest trade-offs
- Because everything runs in the browser, very large or scanned PDFs are bounded by the user's device memory rather than a server.
- Pyntra provides the document engine and hooks, not a finished UI — you build (or adopt an adapter for) the interface.
Frequently asked questions
Does any document data leave the browser?
No. All parsing, editing, and encryption happen client-side. This is the core privacy guarantee — there is no upload step unless you add one.
Can it open password-protected PDFs?
Yes. Pyntra supports encrypted PDFs using RC4, AES-128, and AES-256, and can re-encrypt on export.
Which UI libraries work with it?
Any. The headless hooks are UI-agnostic; there are adapters for Material UI and Tekivex UI, or you can wire your own components.
Tekivex · open-source enterprise developer tools · MIT licensed · Products · Use Cases · About · TekiVex UI