Author: Λ - BoltQuickTools

Who I am

I am a full-stack web developer with more than five years of professional experience, working primarily with JavaScript, TypeScript, Python, and the modern browser platform. My day job involves building production web applications for small and mid-sized businesses. BoltQuickTools is the side project I run on evenings and weekends to scratch my own itches around fast, private, single-purpose tools.

I am not a venture-backed startup. I do not have a content team. Every tool on this site exists because I needed it, or because a friend or reader asked for it, or because I saw an existing online tool doing something badly and thought I could do it better.

Why I build these tools

Most utility websites you find on a Google search for "JSON formatter" or "Base64 decode" share two problems. First, they ship megabytes of JavaScript before they do anything useful, which is absurd for a tool that should do one job in a fraction of a second. Second, they often send your data to a server for processing, which means a stranger's machine briefly handles your API tokens, your customer PII, or your private image files. Neither of those is acceptable to me.

So I write tools that load in under a second, ship a single self-contained HTML file with inline JavaScript, and process everything locally using standard Web APIs. The Network tab in your browser DevTools is the proof: open any tool, then use it, and you will see no outbound requests for the data you typed in.

How I work

Every tool starts the same way. I sketch the UI on paper, write the core algorithm in a scratch file, then collapse the whole thing into one HTML document. I do not use a framework. I do not use a bundler. The build step, if you can call it that, is a Python script that generates the sitemap and the category pages. Total page weight per tool sits between 12 and 60 KB compressed.

When I make a change, I test it on Chrome, Firefox, Safari (via Playwright), and at least one mobile browser before publishing. Tools that handle untrusted user input get explicit sanitization passes. Tools that touch the clipboard or filesystem ask the browser, never roll their own hack.

What I care about

Privacy

I would rather lose a feature than ship a tool that secretly phones home. There is no analytics tracker on this site that watches what you paste.

Speed

If a tool takes more than 200 ms to respond on a mid-range laptop, I treat that as a bug.

Correctness

Tools that parse formats (JSON, YAML, TOML, regex) are tested against the official spec corpora where available.

Transparency

I tell you exactly what runs in your browser and what does not. If a tool needs to fetch a model from a CDN (e.g. OCR), that is documented on the page.

Get in touch

The fastest way to reach me is by email at [email protected]. I read everything that lands in that inbox, including bug reports, feature requests, and the occasional polite disagreement about tool defaults. Replies usually go out within 48 hours.

If you found a serious security issue, please put "security" in the subject line so I can prioritize it. I have not had to issue a security advisory yet, but I would rather hear about a problem from you than from a stranger on social media.