About mtools – mtools

These are all tools I’ve regularly needed myself over the years, but I never found a go-to option that offered the right features without compromising on privacy and security. Building them with privacy in mind from the outset, and bringing them all under one roof, has made it much quicker, easier and more reassuring whenever I need one of them. Hopefully it will do the same for you!

Richard Lucker – creator, mtools

Why it exists

Many online tools of this kind send whatever you paste to a server, show adverts and track their visitors. That is a poor fit for tokens, configuration and customer data. mtools does the work on your own device instead, so you can use it with material you would not paste into a website.

Principles

Your data stays with you. Every tool runs in your browser, and the site's security policy stops pages from sending anything. See Privacy.
No tracking. No cookies, analytics, adverts or third-party scripts.
Fast. Each page loads only the code its tool needs, with strict size budgets checked on every change.
Accessible. Built to WCAG 2.2 AA, with keyboard and screen-reader support. See Accessibility.
Correct. Tools follow the relevant standards and are tested against published test vectors and independent implementations.
Built on permissive open source. The few libraries used are listed on the third-party notices page.

Check it yourself

Open your browser's developer tools, choose the Network tab, and use any tool. Once the page has loaded, no requests are made, whatever you type.

Get in touch

I’ve got more tools in the pipeline, including diff tools and a tool for creating simulated JSON payloads. Suggestions and bug reports are welcome on the feedback page on GitHub, and questions through the contact page.

You can see what has changed recently in the changelog.