But almost none of them let you create tools tailored to your own workflows — most are fixed, one-size-fits-all utilities.

On top of that, many of these sites require uploading your files to their servers, which raised privacy concerns for me.

So I built ToolBake: a platform where you can create your own tools and run them locally in your browser.

Initially, ToolBake allowed users to define their own UI and handler logic manually. But I quickly realized that asking people to write code and design UIs for every small tool is still too much friction.

One of the original design goals was therefore to combine this customization model with good prompt engineering, so users can describe what they want and let an LLM generate the UI widgets and handler code as a starting point — which they can then inspect, tweak, and extend.

With ToolBake, you can:

- Define your own tool UI and logic directly in the browser

- Run tools locally (no server processing, no data upload)

- Use real capabilities like ffmpeg, ffprobe, ImageMagick, and extend with npm packages

- Optionally use AI assistance to generate UI widgets and handler code

The goal is to combine:

- the flexibility of scripting

- the convenience of a UI

- and the privacy of local execution

ToolBake can be used directly on the hosted site, or self-hosted by running a single Go binary (no runtime dependencies).

All official tools on the demo site are built using the same tool customization mechanism available to users. They are not hardcoded features.

You can inspect these tools to see what the system is capable of, and you can build tools just as powerful by defining your own UI and handlers.

Live demo: https://toolbake.com

GitHub: https://github.com/WonderfulSoap/ToolBake

I’d love feedback on:

- the execution model - security assumptions - and what kinds of tools you’d want to build with this