RunLocalTools

Roadmap

Building a better kind of tool platform.

RunLocalTools is growing, but the goal isn’t simply to publish as many tools as possible.

The goal is to build useful, capable software that runs locally in your browser.

That means adding tools, but it also means improving the tools that already exist, connecting related workflows and making the entire platform easier to use.

Browse everything that’s live →

What we’re building toward

More capable tools

A RunLocalTools tool shouldn’t stop at the most basic version of a task when better functionality can be provided locally.

We’re continuing to expand tools with deeper controls, better workflows, useful exports and features that would often be hidden behind paid plans elsewhere.

Connected workflows

Individual tools are useful.

Groups of tools that work together are much more useful.

For example, a workflow might involve:

Clean data → transform it → convert it → export it.

Or:

Resize an image → compress it → remove metadata → download it.

Or:

Merge PDFs → manage pages → edit metadata → redact information → compress the result.

As the library grows, we’re interested in making these relationships easier to discover.

Stronger category ecosystems

RunLocalTools already spans areas including:

  • Image
  • PDF
  • Text & Developer
  • Spreadsheet
  • CSS & Tailwind
  • Video & Audio
  • Social & Creator
  • Privacy
  • Finance
  • Business & Career
  • Everyday utilities

Some categories are becoming substantial software ecosystems in their own right.

The roadmap is therefore not just “add another tool.” It’s also about making the tools within each category work better together.

Better local processing

Local processing is fundamental to the platform.

As browser technology improves, we’ll continue looking for ways to move more capable workloads into the browser while keeping the experience practical on normal devices.

Better usability

Powerful functionality isn’t useful if people can’t figure out how to use it.

Future work will continue to improve interfaces, defaults, file handling, previews, exports, responsiveness and the general experience of moving through the toolkit.

More ways to use the platform

RunLocalTools isn’t limited to people visiting the website directly.

The platform already supports embedded tools, and private deployment can be discussed for organizations with more restrictive environments.

See Embed Our Tools and Enterprise & Self-Hosted for more.

What we don’t want to build

We don’t want RunLocalTools to become a giant directory of shallow tools that technically exist but aren’t worth using.

We would rather have a smaller number of genuinely useful, well-built tools than thousands of thin pages created simply to increase a number.

Quality matters.

How we choose what comes next

Priorities can come from several places:

  • Repeated user requests
  • Problems we encounter ourselves
  • Gaps in existing workflows
  • Opportunities to replace an unnecessarily complicated service
  • Improvements that can be performed effectively in the browser
  • Tools that complement existing parts of the platform

The roadmap will change as the platform changes.

If there is something you want to see, send us a tool request.