Methodology
How the tools are built,
and how they are checked.
utils.sbs is a catalogue of 585 browser-based tools across 29 categories. Processing happens on the device whenever the browser platform allows it, and every tool page explains its input, output, supported engine, calculation method and limitations.
Reviewed by the utils.sbs team · Updated November 2026
Local-first
Files are decoded and processed in the tab with browser APIs. There is no upload step for the tools that support local processing.
One job per page
Each tool has a focused workspace. Larger editing workflows live in a separate studio, so a tool page does not grow into a suite.
Explicit limits
Every page states the engine, supported formats and known limitations instead of hiding device or browser constraints behind a spinner.
The architecture
The browser is the computer.
Images are decoded and transformed with the Canvas API. PDFs are parsed and rebuilt with pdf-lib. Audio uses the Web Audio API. Video uses canvas, MediaRecorder and WebCodecs where available. Text, data, JSON and developer tools use JavaScript in the page.
A tool page lists the engine it uses under “At a glance”. That engine is the same one used by the workspace on the page. When a browser does not expose a required API, the tool explains the limitation instead of silently uploading the file.
Studios are separate full-page workspaces for larger media jobs. They use the same local-first approach and are linked from the relevant category and tool pages.
Calculations
Reference results, not black boxes.
Calculator pages show the formula or method used. The result is computed from the values entered in the page with standard JavaScript arithmetic and displayed with the relevant units. Where intermediate values help, they are included in the result panel.
Calculations are reference tools. They are not financial, medical, legal or safety-critical advice. Important decisions should be verified against the source formula or a qualified professional.
Browse the calculator shelf to see the formula shown on each page.
Review process
Every tool page is checked against the same checklist.
Each page states what the tool does, its input and output formats, the engine it uses and its known limitations. Calculator pages add the formula. Media pages add privacy and browser-support notes.
Pages are reviewed when a tool changes. The review date is shown on the page, and the sitemap is regenerated with each build so search engines and agents see the current set of tools.
The catalogue is intentionally focused: one tool per job, a dedicated page for each tool, and a category index that links every page. There are no accounts, no upload endpoints and no per-file limits imposed by a server queue.
References
Primary sources for the engines we use.
Machine-readable
For search engines and agents.
The full catalogue is also available as plain text for AI assistants and agents, alongside the sitemap used by search engines.