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 ships in 15 languages, installs as a Progressive Web App for offline use, and is open source under the MIT license.

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 JXXR1, working independently. No company, no funding round, no investors, no exit timeline. Decisions about which tools to build, which languages to support, and how the site is monetised are made by the maintainer alone, against the principles documented further down this page. Contact and contributions go through GitHub Issues.

How it works technically

Toolhub is a static site of pre-rendered HTML hosted on GitHub Pages, served via Cloudflare for HTTPS and edge caching. 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 (in production) AdSense ad slots. Tool inputs never reach our infrastructure because there is no infrastructure to reach. The exception is tools that explicitly fetch a known third-party resource (e.g., the YouTube Thumbnail tool, which loads an image from YouTube's CDN) — these are documented on each tool's help block.

Open source

The complete source code is at https://github.com/JXXR1/Toolhub under the MIT license. Every tool's computation logic is inspectable. Anyone can fork the project, run it on their own infrastructure, or contribute back via pull request. Contributions, bug reports, and tool ideas are welcome via GitHub Issues. There is no proprietary core, no "open source frontend, closed backend" split.

No AI slop

Tool help blocks, articles, and About-page content are written by a human, not generated by an LLM. Translations to the 14 non-English languages use machine translation as a starting point and are then reviewed within reason — Italian and English get the most attention because the maintainer is native or fluent in both. Smaller languages are corrected via GitHub issues from native-speaker community contributors. If you spot a translation that reads as robotic or wrong, open an issue — it is an easy fix and exactly the kind of contribution that makes the site better for everyone.

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 by default. Tools run as JavaScript in the visitor's browser. There is no server-side processing of inputs. The only exceptions are tools that explicitly fetch a known third-party resource (the YouTube Thumbnail tool, which loads an image from YouTube's CDN). When an exception applies, it is documented on the tool's help block.
• 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.
• Access in 15 languages. Toolhub ships in English, German, Spanish, French, Italian, Portuguese (BR), Polish, Japanese, Dutch, Turkish, Indonesian, Vietnamese, Hindi, Slovak, and Czech. Languages were chosen for being either large native populations (Hindi, Indonesian, Vietnamese), under-served regional populations (Slovak, Czech, Polish), or having strong developer communities (German, Japanese, Brazilian Portuguese).
• Open source, MIT-licensed. The entire codebase is on GitHub. Contributions, bug reports, and tool ideas are submitted as issues or pull requests. There is no proprietary core, no "open source frontend, closed backend" split.

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 written by a human. Every tool's help block — "Common gotchas," "Pairs with," "How it works" — is written, not generated. Translations to the 14 non-English versions are reviewed within reason; bad translations are corrected via GitHub issues.
• 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. When AdSense approval lands, ads will appear in clearly-marked slots — not interspersed with the tool UI, never as popups, never as autoplay video. The tool itself will always be usable without dismissing 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.
• 15 languages, deliberately. Most utility sites are English-only or use auto-translated machine output. Toolhub's translations are human-reviewed in the major languages and corrected via community issues for the smaller ones.
• 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:

• Weekly editorial article. Every Sunday an editorial article is published — a deep-dive on a tool, a "common production gotcha" piece, or a "when to use X vs Y" comparison. The archive lives at /articles/.
• Quarterly data refresh. Tools that depend on external data — VAT rates per EU country, US state sales-tax nexus thresholds, healthcare-related rules in the medical tools, currency conversion references — 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 filed on GitHub 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.

Languages and accessibility

Toolhub is published in 15 languages and follows WCAG 2.1 Level AA practices wherever achievable on a static-site stack:

• Languages. en (English), de (German), es (Spanish), fr (French), it (Italian), pt (Portuguese — Brazil variant), pl (Polish), ja (Japanese), nl (Dutch), tr (Turkish), id (Indonesian), vi (Vietnamese), hi (Hindi), sk (Slovak), cs (Czech). Each language has its own URL path (e.g., /de/json-formatter/) with hreflang annotations to help search engines route users to the right variant.
• Direction. All current 15 languages are left-to-right. Right-to-left languages (Arabic, Hebrew, Persian) are intentionally not yet supported because RTL support requires layout work beyond translation alone, and shipping it half-baked would be worse than not shipping it.
• 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. The closest thing to a "user" Toolhub knows about is an anonymized page-view in Cloudflare Web Analytics when that integration is on.
• Not "open source theatre". The codebase is genuinely on GitHub at https://github.com/JXXR1/Toolhub — fork it, self-host it, contribute back. Every tool's logic is inspectable.

Contact and contribution

The primary contact channel is GitHub Issues. Use it for:

• Bug reports — incorrect calculations, broken downloads, accessibility regressions, translations that look wrong
• Feature requests — new tools, additional languages, accessibility improvements
• Privacy or security concerns — anything that looks like Toolhub is leaking data unintentionally
• Translation corrections — particularly welcome for languages where the maintainer is not native

For matters that are not appropriate for a public issue, the email contact in the GitHub profile is the route.