Roadmap
Grouped by what is actually blocking each tool rather than by quarter. A date we would miss is less useful to you than knowing the real obstacle.
What comes next, in order
- Done: text recognition in the browser. Scanned PDFs and photos of documents can now be read on the device, free, in English, Urdu and Arabic. More languages are a small addition each.
- 1. The PDF organise workspace. A visual page manager where reordering, rotating, deleting and inserting happen together. Today those are four separate tools, which is four times the work for one job.
- 2. Signing and filling PDFs. Placing a signature and completing forms need an on-page editor, which is the next interface to build.
- 3. Video re-encoding. Audio conversion, GIFs and frame grabs already work. Compressing and converting video itself is deferred deliberately: the in-browser build is roughly 25 MB of WebAssembly, which must be lazy-loaded behind an explicit prompt rather than inflicted on every visitor.
- 4. Chained workflows. Only worth building once the steps it chains exist. Shipping the engine first would produce a workflow builder with nothing to build from.
Available now (82)
Working in this deployment with no configuration. All of these run on your own device.
Available now
Need a paid AI service (45)
These depend on a paid AI service. This site runs only tools that are free and work on your own device, so they are not switched on.
Need a paid AI service
Needs a processing engine (24)
These need something substantial that is not bundled: a full video engine for re-encoding video, a document layout engine for faithful Office conversion, or PDF encryption. Each is a deliberate decision about download size and cost, not an oversight.
Needs a processing engine
Specified, not built (16)
The behaviour and processing approach are settled; the interface is not written. These are ordinary build work rather than blocked on anything external.
Specified, not built
Two tools that are not on this roadmap
Watermark removal and downloaders for third-party platforms are not listed as planned, delayed or blocked. They are declined. Both have real search demand and declining them costs traffic — which is rather the point of having a position. The reasoning is here.
These counts are generated from the tool registry at build time — 82 live, 45 awaiting configuration, 24 awaiting an engine, 16 not yet built — so this page cannot describe a state the code is not in.