Paste it. Fix it.Never upload it.
68 free tools for text, code, colors, numbers, and the web. Whether you are a developer, a designer, or just need something converted, it runs instantly in your browser and your data stays on your machine.
Paste your data and it opens the right tool with the result ready, or type a word to search. No account, no install, nothing to learn.
Use it from your agent. No copy-paste.
The network tools, the ones that reach real infrastructure, are available over MCP. Point Claude or any MCP client at toolhq and it can run a DNS, SSL, or IP check on its own. The local tools keep running in your browser.
$ claude mcp add toolhq https://toolhq.io/api/mcp
{
"mcpServers": {
"toolhq": {
"url": "https://toolhq.io/api/mcp"
}
}
}Compatible coding agents
claude mcp add --transport http toolhq https://toolhq.io/api/mcp
Every tool. All free.
68 utilities that load instantly. Search below or browse by category. Most run entirely in your browser; network tools say exactly where your data goes.
Loading tools…
Three steps. Ten seconds.
- 01
Pick a tool
Search or browse 68 tools for text, code, colors, numbers, and the web. Every one loads instantly.
- 02
Paste your data
JSON, a token, a color, a cron expression. It is processed right in your browser, not on a server.
- 03
Copy the result
Live output with one click copy. No account, no install, no waiting, and nothing left behind.
Guides for the things you debug.
Practical, no-fluff writing on JSON, JWTs, DNS, SSL, regex, and more — written alongside the tools that fix them.
Can you use comments in JSON? No, and here is what to do
JSON does not support comments by design. Why Douglas Crockford removed them, what error you get, and the real options: JSONC, JSON5, dummy keys, or a different format.
How to flush your DNS cache on any system
The exact commands to clear the DNS cache on macOS, Windows, and Linux, plus the browser's hidden cache, when flushing actually helps, and why it cannot speed up propagation.
HTTP/1.1 vs HTTP/2 vs HTTP/3: what actually changed
What each HTTP version changed and why: head of line blocking, multiplexing, header compression, and why HTTP/3 abandoned TCP for QUIC. Plus how to check which version your site uses.
Your data never leaves
your browser.
Local by default
Formatters, decoders, and generators run as plain JavaScript on your machine. Turn off your wifi and they still work.
No tracking, no accounts
No tracking cookies, no ad pixels, no sign ups. Page views are counted anonymously and that is all. Local storage stays on your device for your theme, language, and recently used tools. The in-browser tools store nothing.
Safe for secrets
JSON, tokens, and unreleased work are safe to paste into the local tools. There is no server on the other end to leak them.
Asked often, answered plainly.
Is toolhq really free?
Yes, every tool is free with no usage limits, no premium tier, and no account to create. The site exists because these tools should just be available.
Is my data uploaded anywhere?
No. The tools run as JavaScript in your browser, so what you paste never leaves your machine. The few tools that need the network (like the API tester and DNS lookup) say exactly where requests go, right on the page.
Do the tools work offline?
Most do. Once a tool page has loaded, formatters, converters, encoders, and generators keep working with no connection at all, because there is no server involved.
Is it safe to paste API keys, tokens, and production data?
For the local tools, yes: there is no server on the other end to log or leak them. Each tool states its privacy behavior in a badge at the top of the page, so you always know before you paste.
How is toolhq different from other online tool sites?
No ads, no popups, no cookie walls, no accounts, and no tracking. Tools load instantly, the privacy promise is real, and the whole site is built to get you back to work as fast as possible.