-
Notifications
You must be signed in to change notification settings - Fork 1
Roadmap
What PaperOtter is working towards, and what it has deliberately decided not to do.
This page is about direction, not dates. PaperOtter is built by one person; an item being here means it is agreed and scoped, not that it is scheduled.
1.0.0 is released, with builds for macOS (Apple silicon and Intel), Windows and Linux. Three things are still open. None of them are new features: they are checks and pages that no automated test can produce.
| Item | Where it stands |
|---|---|
| A visual pass over the UI | Open. Automated tests render no pixels, so nothing has checked that the layout still looks right at every window size, in both themes |
| A proper home page | Written and verified. Waiting on the switch to GitHub Pages |
| Proof that cancelling a batch stops the work | Reopened. The test that covered this was built around Ghostscript, which has since been removed, so it can no longer run. The cancel itself is unchanged; what is missing is the proof |
Closed: the version number is settled at 1.0.0; the README's dependency claims were checked line by line and were already accurate; and the German interface has now been read end to end, including the six warnings about losing work that nobody had read in German before.
Compress PDF already lets you save a named setting and pick it up again later. The same idea belongs in the two tools where the settings repeat the most.
A watermark is the clearest case: text, opacity, rotation, position, size and colour, set once and then wanted on every document for years. Page numbers are the same story: position, format, size and starting number are house style, not a per-document decision.
Presets will work the same way whether you use the standalone tool or the matching panel inside Edit PDF. A preset saved in one appears in the other.
Deliberately not everywhere. Tools like Split, Merge, Rotate and Organise are per-document decisions, where a saved preset would save a single click. Convert Image and PDF to JPG are plausible later, once presets have proved themselves in the first two.
Turn a document into something an AI model can actually work with, without it ever leaving your machine.
- Clean Markdown, structure kept. Word heading styles become real headings, emphasis survives, and Word's invisible formatting noise is stripped. Where chapter markers are inconsistent, PaperOtter flags them for you rather than guessing.
- Split by heading, into one file per chapter or section, plus the whole document as a single file.
- Export presets for the shape you need: the whole document, chapter by chapter, or both.
The point is preparation, not analysis. PaperOtter prepares; your own AI reasons. You already have a model you trust. PaperOtter's job is to hand it the thing it cannot make for itself: a clean, structured, local bundle.
What this will not do, and why. Chapter summaries, automatic story bibles and continuity-contradiction reports have all been suggested, and all of them need a language model. That means either bundling one: breaking the promise that PaperOtter needs no other software installed, or sending your document to a cloud service, which breaks the more important promise on every screen of this app: your files never leave your device. For anyone working on a confidential manuscript, that promise is the whole reason to use PaperOtter. So those steps stay out.
- Cloud processing, accounts, or sync. PaperOtter runs on your machine. That is the product, not a limitation of it.
- Telemetry or usage analytics. Nothing is collected, so nothing is sent.
- Saved passwords, in presets or anywhere else.
Have a use case that is not here? Open an issue: the tools that exist today came from people describing what they were stuck doing by hand.
Home 🏠 | Common Tasks 🎯 | Required Dependencies | Using PaperOtter | Troubleshooting | FAQ ❓
Feature guides: see the sidebar for a page-by-page walkthrough of every tool.