Roadmap

Shipped today — v0.1.0

• Viewer with thumbnails, zoom, fit modes and keyboard navigation
• Page operations: reorder by dragging, rotate, delete, duplicate, extract, merge, split
• Annotation: text boxes, highlights, freehand ink, shapes, images, drawn signatures
• Fill and flatten existing AcroForm form fields
• Stamp Studio — layouts, frames, inks, distress, variable fields, PNG export, .stamps packs
• Workflows — record, edit, save as a file, run on one document or a folder
• Bates numbering, page numbers, headers, footers, watermarks, metadata removal
• Batch processing: folder in, ZIP out, entirely on your machine
• Local Processing Monitor and Safe Mode, with every export reopened and verified
• Offline support and a single-file portable build
• Permanent redaction — Find & Cover now actually removes the marked text from the page's own structure on export, independently re-verified, not merely covered
• In-browser OCR — a self-hosted engine that makes a scanned page's text genuinely searchable and editable, reaching both the form builder and the main editor's own Edit Text and Find tools
• Auto-actions — live rules that react while you edit ("when I place a signature, place a stamp near it"), optionally scoped to one specific named, saved signature
• Export directly as JPG, PNG, or plain text, not only PDF, without leaving the editor
• Named, multiple saved signatures — save several signatures per profile, matched to a specific auto-action rule, not only the original one-at-a-time quick-sign
• Recoverable local work — in-progress edits autosave to this browser only; an accidentally closed tab does not lose the work
• Workflow library — save a workflow in this browser and run it again with no file to re-upload, alongside the original file-based (record → save → email) flow, which still works unchanged
• Installable as a real PWA, with a working offline service worker
• A bookmarklet that opens whatever PDF you're already viewing directly into the editor, in one click, browser tab to browser tab — never through a server
• Form builder, rebuilt — 50 starter templates across every common category, with search and filtering, plus a plain-language description parser that matches an archetype and explains its own reasoning. No LLM, no API key, no network request

Shipped since v0.1

• Workflows — save the steps you take on one document as a file, run them on a folder, share the file itself
• PDF X-ray — metadata, embedded scripts, attachments, hidden text and earlier revisions
• Reusable signature — draw once, place again with one click
• Find & Cover — search for a pattern (email, phone, ID number), and actually remove the matched text from the page's own structure on export, not just draw a block over it. How that actually works. The one stated exception: a rotated page is covered but not yet removed, and the tool says so on screen at the moment it applies, not buried here.
• Activity log — a local, on-device record of exports and workflow runs, never transmitted
• Conditional workflow steps — any step can run "only if" the page count, filename or presence of text matches a condition
• Rename from content — a workflow step that reads text on the page and uses it to name the output file
• Compare two PDFs — a word-level diff, page by page, of what changed between two versions
• Watch a folder — Chrome and Edge only. A workflow applies automatically to anything dropped in a chosen folder while the tab is open

Not shipped, and honestly labelled

Tracked, multi-party e-signature requests

Sending a document out for signature and watching its status change as each person signs, with a completion audit trail. What exists today places a visual signature on a page you already have open; it does not yet send anything to anyone else or track what happens after.

Cloud storage connectors

Importing from or exporting to Google Drive, Dropbox, or OneDrive directly. Not built yet, and worth being explicit about the tension it would create: this product's entire promise is that your document never leaves your device unless you choose to send it somewhere, so this needs to be built as an explicit, user-initiated action each time — never a background sync — or it should not be built at all.

Decided against

How priorities get set

By what people actually hit, not by what sounds impressive. If a PDF fails to open, that outranks any new feature on this page. Tell us what broke — awkward files are how this gets better, and they end up in the test corpus so the same thing cannot break twice.