About Web Toolkit
Web Toolkit is a collection of 21 small utilities across 5 categories. Every one of them runs entirely inside your browser.
Why another tools site
Most online utilities are one of two things: a thin wrapper around a server endpoint that receives whatever you paste, or a page so covered in advertising that finding the input box takes longer than the task. This site is built to avoid both.
How it works
- Nothing is uploaded. Formatting, hashing, encoding and image processing all happen with browser APIs on your own machine. Load a tool page, disconnect from the internet, and it still works.
- No accounts. There is nothing to sign up for and no paywall on any tool listed here.
- The tool comes first. The first screen of every page is the tool itself — never a banner, a cookie wall or an advertisement.
Languages
The site is published in English. Every tool page, including its FAQ and explanatory text, is also written in Traditional Chinese, Japanese, Spanish and German, but those versions are not published yet. A language goes live only once there is evidence that people look for these tools in it, and then one language at a time rather than all five at once.
How it is paid for
The site is static and costs close to nothing to run. Advertising may appear below the tool, in the sidebar on wide screens, and between content sections — never inside or above the tool, and never as a full-screen interstitial. If advertising ever measurably degrades the experience of moving from one tool to the next, the placement gets removed rather than the standard lowered.
Built with
Astro for static rendering, React islands for the interactive parts, and Cloudflare Pages for hosting. Fonts are self-hosted so no request goes to a third-party CDN.
Who runs this
Web Toolkit is built and maintained by Ikonode, an independent software studio that has published the site since 2026. There is no company hierarchy behind it and no venture funding. The same small team writes the code, the explanatory text and every guide on this site, decides what gets built, and answers the email — the byline on each guide and the "maintained by" line under each tool point back here because it is the same people throughout.
The site grew out of a working developer's own toolbox: a set of scripts for reformatting JSON, decoding tokens, working out date ranges and resizing screenshots that had been copied between machines for years. Publishing them as browser pages made them usable from any computer without installing anything, and without handing the data to a server. That origin is why every tool here is one that has been used in earnest before it was written up.
Written enquiries, corrections and takedown requests all reach us at hello@ikonode.com, and the contact page lists what to expect a reply about.
How the tools are verified
A tool page says three things about a tool: how to use it, what a real run produces, and what it does not do. Each of those is checked in a specific way before it goes live, and re-checked whenever the code changes.
- The logic has tests. The formatting, parsing, hashing, date and calculator code lives in a shared library with a unit-test suite that runs on every build. A change that breaks an existing case fails the build; the page cannot deploy with it.
- The worked example is a real run. The input and output shown on each tool page were produced by pasting that exact input into that exact tool, not typed from memory. If the code changes so that the output would differ, the example is regenerated, not left to drift.
- The explanatory text is read against the code. Every sentence that describes what a tool does is compared with the implementation before publishing. Two claims were corrected this way in September 2026 — the word counter counts UTF-16 code units rather than user-perceived characters, and the case converter has no slug mode — and the pages now say what the code actually does.
- Limits are stated, not discovered. The "what this tool does not do" section is written from the failure cases found during testing: that image conversion through a canvas discards EXIF metadata and embedded colour profiles, the threshold at which a bare number is read as milliseconds rather than seconds, and so on.
- A date is attached. The "last checked" date under each tool is the day the page's text, example and limits were last compared with the code in full. The current date is 2026-09-11. When a tool changes, the date changes with it.
If you find a case where the tool and the page disagree, that is a bug in the page as much as in the tool. Send the input and the expected result to hello@ikonode.com and it gets fixed with the date updated.
Editorial policy
- Every tool is used before it ships. A tool is added when we needed it ourselves or someone asked for it, not to fill a keyword gap.
- Explanations are written by hand. The FAQ and the notes under each tool exist to answer the question people actually arrive with. Where a number appears — a size limit, a percentage, a format threshold — it is one we checked, not one we remembered.
- Corrections are made in place. If a calculation or an explanation is wrong, tell us and it gets fixed, with the "last updated" date on the affected page changed to match.
- Advertising never decides content. No tool, guide or recommendation on this site is paid for, sponsored or ranked by what earns more. Advertising placement is described on this page and in the privacy policy; it has no influence on what we say about anything.
Suggestions
Missing a tool, or found a bug in a calculation? Let us know — the tool list grows based on what people actually ask for.