Request a feature

Describe the task, not the button

The most useful requests explain what you are trying to finishrather than which control you expected to find. "I need to send 40 scanned receipts to my accountant as one file under 10 MB" tells us far more than "add a batch option" — and it sometimes turns out an existing tool already does it, which means you get an answer the same day instead of waiting for a release.

Worth including:

• The input you start with and the output you need.
• How you handle it today, and what makes that painful.
• How often it comes up — daily, weekly, once a quarter.
• Any tool elsewhere that gets it right, so we can compare.

What we say yes to

• It runs in the browser

  Every tool here processes files on your own device. A feature needing a server — OCR at scale, heavy video encoding — breaks that promise, so we would rather not build it than quietly start uploading your files.

• It finishes a real task

  The tools that earn their place turn one file into the file you actually needed. A setting nobody can explain the purpose of tends not to survive.

• More than one person wants it

  Overlapping requests are the strongest signal we get. A niche ask still gets read; it just waits behind the ones several people described independently.

• It fits in one screen

  If a tool needs a manual, it is two tools. Requests that split cleanly into simple steps ship much sooner than all-in-one suites.

After you send it

We read every request and reply — including when the answer is no, with the reason. We do not publish a dated roadmap, because a two-person toolkit that promises delivery dates ends up missing them. What we do instead is tell you when the thing you asked for goes live.

Reporting something broken rather than missing? Use the bug page. Curious what already exists? The about page lists the current toolkit, and the FAQ covers the limits people run into most.