About Toolhub

What Toolhub is

Toolhub is a collection of free developer and everyday utility tools that run entirely in your browser. There is no signup, no account, no tracking, no server-side processing. Paste data in, get the result, close the tab — nothing is stored or transmitted. The site installs as a Progressive Web App for offline use.

Why it exists

Most online utility sites are ad-saturated parking pages, freemium SaaS with rate limits, or single-tool sites where the maintainer moved on three years ago. The data you paste in often gets logged, sometimes for spam detection, sometimes for training data, sometimes for resale to brokers. Toolhub exists because that pattern is fixable: a static site that runs computation in the browser solves the same problems without any of the data risk. One page per tool. Runs locally. Leaves you alone.

Who maintains it

Toolhub is built and maintained by Toolhub Admin (GitHub: JXXR1), a software developer working independently. No company, no funding round, no investors, no exit timeline. Decisions about which tools to build and how the site is monetised are made by the maintainer alone, against the principles documented further down this page. Contact is by email at contact@toolhub.software.

How it works technically

Toolhub is a static site of pre-rendered HTML hosted on Cloudflare Pages, with HTTPS and edge caching built in. Every tool runs as JavaScript inside the visitor's browser — there are no API endpoints, no backend services, no database. The only network requests after the page loads are for fonts and AdSense ad slots (after consent). Tool inputs never reach our infrastructure because there is no infrastructure to reach.

Transparency

Every tool runs as JavaScript inside your browser, so its computation logic is fully inspectable — open your browser's developer tools and watch exactly what runs. There is no server-side processing, no proprietary backend, and nothing about a tool's behaviour that is hidden from you. Bug reports, corrections, and tool ideas are welcome by email at contact@toolhub.software.

On AI and quality

Tool help blocks, articles, and About-page content are human-written or human-reviewed, not auto-generated and published unchecked. AI tools are used only as a drafting aid — every published page is read and corrected by a human before it ships. If something reads as robotic, wrong, or misleading, the contact email at the foot of this page gets it fixed.

Experience and expertise behind the tools

Toolhub is built and maintained by JXXR1, a working software developer, and the tools reflect that hands-on background rather than a marketing team's idea of what a "tool page" should contain. The site exists because its maintainer hit these problems in real work — malformed JSON at 2am, LLM token bills that needed forecasting, VAT rules that change per country, regex that behaved differently than expected — and wanted a fast, private, correct place to solve them. Every tool ships from that test: it has to be something the maintainer would reach for personally.

Correctness is treated as the product, not a nice-to-have. Where a tool encodes a standard or a formula, that logic is taken from the primary source and cross-checked against it:

• Specifications, not blog posts. Encoding, hashing, and web-standard tools follow the governing RFCs and W3C specifications directly (for example RFC 4648 for Base64, RFC 7519 for JWTs, the WCAG contrast formulas for the accessibility checkers). The editorial articles cite the same primary sources so readers can verify the claims themselves.
• Authoritative references for domain math. Finance tools follow published guidance (compound-interest and amortization identities, CFPB consumer-finance guidance); security guidance follows NIST publications such as SP 800-63B; tax tooling follows the relevant tax-authority documentation. Numbers on the site trace back to a checkable source, not to an unattributed round figure.
• Verified against reference behaviour. Where a reference implementation exists, a tool's output is checked against it — a UUID validates against the RFC's variant/version rules, a cron expression parses to the same schedule a standard cron daemon would run, a Base64 round-trip matches the platform's own decoder.
• Corrections are welcome and acted on. If a calculation is wrong, that is a bug, and it is fixed in the same week where feasible. Because every tool runs as readable JavaScript in your browser, you can inspect exactly what it does in DevTools and challenge it rather than take it on trust.

This is the practical meaning of "expertise" for a utility site: not credentials on a page, but tools whose logic is inspectable in the browser, sourced to the relevant standard, and fixed promptly when it is wrong.

Principles Toolhub is built on

Five principles run through every tool on the site. They predate any specific tool and outlast any specific implementation:

• Browser-only. Every tool runs as JavaScript in the visitor's browser. There is no server-side processing of inputs, and no exceptions.
• No tracking, no analytics, no fingerprinting. Toolhub does not load Google Analytics, Plausible self-hosted analytics, Fathom, Matomo, or any equivalent. The site does not set cookies for tracking. The optional Cloudflare Web Analytics integration is gated behind config that ships disabled by default; when enabled, it uses Cloudflare's cookieless, IP-anonymised counter.
• No signup, no account, no upload. There is no login. There is no rate-limited freemium tier. There is no "sign up to unlock" pattern. Pasting a JSON document into the JSON Formatter does not send the document anywhere — it stays in the visitor's tab.
• English, done properly. Every tool, help block, and article is written and reviewed in English rather than machine-translated across dozens of half-checked locales. One language, held to a real quality bar.
• Static and self-contained. The site is pre-rendered HTML with no backend, no database, and no API. There is nothing server-side that could quietly start collecting data between visits — what runs is what you can see in your browser.

How tools get built

The build process is opinionated. A new tool reaches the site only after passing a checklist:

• Solves a real, recurring need. The bar is "I would use this tool myself" — not "this is interesting to build". The Token Counter tool exists because LLM API cost management is a real ongoing problem; the Compound Interest Calculator exists because savings projections are a recurring personal-finance need.
• Computation fits in the browser. If a tool would need server-side compute (large file processing, machine learning inference, hosted databases), it does not get built. Toolhub is not the right platform for it.
• Help block is human-written or human-reviewed. Every tool's help block — "Common gotchas," "Pairs with," "How it works" — is written or reviewed by a human, not auto-generated and published unchecked.
• Lighthouse-clean. Accessibility, performance, and SEO scores are checked before a tool ships. Any score below 95 blocks the merge.
• Privacy-statement reviewed. If the tool touches user input in any way that changes the privacy story (e.g., a new external API call), the Privacy and "How We Handle Your Data" pages are updated in the same commit.

What makes Toolhub different from other "free tools" sites

The market for free online utilities is crowded. Most sites in the category fall into one of three patterns: ad-saturated parking pages, freemium SaaS with rate limits, or single-tool sites maintained by one developer who moved on years ago. Toolhub aims to be different on five concrete axes:

• Ads gated, not pervasive. Ads appear only in clearly-marked slots — never interspersed with the tool UI, never as popups, never as autoplay video. Ad requests are paused by default; in the EEA/UK, a consent banner asks for your choice before any advertising cookies are set. The tool itself will always be usable without seeing an ad.
• No data leaves the browser. Competitors that "format your JSON" routinely log every submission for spam-detection or training data purposes. Toolhub's JSON Formatter runs in your tab; the JSON never reaches our server because there is no server-side endpoint.
• Installable as an app. Toolhub is a Progressive Web App. Installing it gives offline access — useful on flights, in low-connectivity areas, or for sensitive operations where you do not want the tool to phone home even accidentally.
• Hand-written help. Every tool ships with a human-written help block — what it's for, common gotchas, a worked example — not an auto-generated stub or a wall of SEO filler.
• Sustainable maintenance. The codebase is small and static. There is no Postgres instance to maintain, no API quota to refill, no JWT secret to rotate. The "infrastructure burden" of running Toolhub for ten years is genuinely close to zero.

Quality and maintenance cadence

Toolhub is actively maintained. The cadence is:

• Editorial articles. Each tool gets a companion deep-dive — a "common production gotcha" piece or a "when to use X vs Y" comparison — reviewed before it ships. New articles land as tools ship, typically a few per month. The archive lives at /articles/.
• Quarterly data refresh. Tools that depend on external data — VAT rates per EU country and currency reference rates — get a quarterly review. When data changes, the tool's help block records the source and the review date.
• Issue response within 7 days. Bug reports sent to the contact address are acknowledged and triaged within a week. Real bugs (incorrect calculations, broken downloads, accessibility regressions) ship as fixes inside the same week when feasible.
• Dependency hygiene. Toolhub has very few dependencies — most tools use vanilla JavaScript with no build step. The few dependencies (font, icon library, service-worker library) are pinned to specific versions and reviewed before updates.
• Lighthouse + a11y monitoring. Performance and accessibility scores are sampled on key pages. Regressions are treated as bugs.

Accessibility

Toolhub follows WCAG 2.1 Level AA practices wherever achievable on a static-site stack:

• Language. Toolhub is published in English. Earlier machine-translated locales were removed rather than shipped at a quality the maintainer could not stand behind.
• Keyboard navigation. Every interactive element is reachable via Tab. Skip-to-content links are present on every page. Focus rings are visible (not outline: none;).
• Screen reader compatibility. ARIA labels are applied to icon buttons and decorative elements. Form labels are explicit. Heading hierarchy follows document outline.
• Color contrast. Both light and dark themes meet WCAG AA contrast ratios for body text. The accent color is tested for color-blind accessibility using the Color Blind Simulator tool that ships on Toolhub itself.

What Toolhub is not

To set expectations cleanly, here is what Toolhub deliberately does not do:

• Not a SaaS. There are no usage tiers, no rate limits, no API keys to manage. If a tool runs in your browser, it runs without quota.
• Not a venture-backed startup. No funding round, no equity, no acquisition path. Sustainability is the goal, not exit.
• Not a content farm. Articles and help blocks are written by hand or reviewed thoroughly. The site does not auto-generate "Top 10 X tools" posts to chase search traffic.
• Not a data broker. No user accounts, no behavioural profiles, no email lists. Toolhub has no concept of a "user" — there is nothing to track.
• Not obfuscated. Every tool runs as readable JavaScript in your browser — open DevTools and watch exactly what it does. Nothing important happens on a server you cannot see.

Contact

The contact channel is email — contact@toolhub.software. Use it for:

• Bug reports — incorrect calculations, broken downloads, accessibility regressions
• Feature requests — new tools, accessibility improvements
• Privacy or security concerns — anything that looks like Toolhub is leaking data unintentionally

For anything sensitive — press, partnership, security disclosure, or anything involving personal data — email contact@toolhub.software.