Skip to content
ToolsVerse
Community driven

Can’t find the tool you need?

Tell us which tool you are looking for. If enough people ask for it, we build it and make it free for everyone.

Submit a requestSee what is being built
Why it matters

Requests decide what gets built

There is no product committee here. The catalogue grows in the direction people push it.

  • Community driven

    The order things get built in is decided largely by what people ask for, not by what is easiest to build.

  • Constantly growing

    New tools ship continuously. A request that arrives today is competing for the next slot, not a queue position in a year.

  • Every idea counts

    Several tools in the catalogue exist because one person described a problem well. A specific annoyance is worth more than a general suggestion.

  • Built for everyone

    Anything built from a request is free for everyone, immediately, with the same no-upload guarantee as the rest of the site.

The form

Tell us what is missing

Four fields, none of them long. The one that matters most is the last: what you are actually trying to get done. A tool request with a real situation attached is worth a dozen without one.

  • No account needed to send one
  • Your draft is saved on this device as you type
  • An email address is optional, and used once

A rough name is fine — “compress a video”, “convert HEIC to JPG”.

Describe the tool itself: what goes in, what comes out.

This is the part that decides what gets built. Concrete beats general.

Only used to tell you when the tool ships. Nothing else, ever.

Saved as you type, on this device only.

Transparency

What is being built

Stages rather than dates. A dated roadmap on a project this size is a promise nobody can keep, and a missed date costs more trust than never publishing one.

  1. Available now

    The published PDF and image tools, each running entirely in the browser.

  2. In development

    The remaining PDF conversions, and the image tools that need a WebAssembly engine vendored and licence-checked before they can ship.

  3. Planned

    Text, data and developer utilities — the formatters, converters and generators that need no heavy engine and can ship quickly.

  4. Being considered

    Video and audio. Both are genuinely hard to do well on-device, and we would rather not ship them than ship versions that fail on real files.

Public request counts and voting arrive with the account system that can store them honestly. Until then a request reaches a person directly, and the roadmap above is updated by hand rather than generated from numbers we have not collected.

Answers

About requests

Can I request more than one tool?
Yes, as many as you like. Send them separately rather than as a list — a request with its own description of the problem is far more likely to be built than one line in a list of ten.
How do you decide what gets built next?
Three things, roughly in this order: how many people have asked for it, whether it can be done well entirely on-device, and how badly the alternatives serve people today. A tool that everyone else does badly is more interesting to us than one that is already solved.
Will you tell me when it is ready?
If you leave an email address, yes — once, when the tool ships. It is used for nothing else, it is not added to a list, and there is no newsletter for it to become.
What happens to my request?
It is read by the people who build the tools. There is no ticketing queue and no support tier; requests go straight to the roadmap discussion.
Can I suggest a change to an existing tool?
Please do. A missing option on a tool that already exists is usually much faster to add than a whole new tool, so those tend to ship quickly.