GizmoBench guides
Client-Side Tools: What They Are and Which Ones to Use

Client-side tools do their work inside your own browser, so the numbers you type and the files you open are processed on your device instead of being sent to a remote server. For everyday calculators, converters, generators, and file utilities, that design is the one we recommend, and it is the one GizmoBench is built around: no uploads, no account, no installation. Below we explain what client-side processing means, compare the three ways people usually get these tasks done, and show which tool in the catalog fits which job.
TL;DR
- Client-side processing means the work runs on your device, usually in the browser, instead of on a remote server (Cloudflare).
- “Works offline” and “your data never leaves the device” are two different properties, and a tool can have one without the other.
- GizmoBench tools run locally in the browser, with no uploads, no accounts, and no installation, across math, money, home projects, cooking, music, documents, images, and technical work.
- Match the tool to the task using the table below, then open the matching page and start.
Table of Contents
- What client-side processing means
- Offline-first and zero-egress are different properties
- Three ways to get a task done online
- Which tool for which task
- How local file processing works in practice
- A worked example: invoicing a client privately
- Choosing a client-side tool: five criteria
- Where GizmoBench fits
- FAQ
- Sources
What client-side processing means
A web page involves two places where computing can happen. The server is a remote machine run by the site’s operator. The client is your own device, and in practice that means your browser. Cloudflare’s explainer describes client-side processes as work that runs on the end user’s device, almost always written in JavaScript, instead of on a remote server.
For a calculator, the difference is easy to picture. A server-side calculator sends your inputs to a remote computer, waits for it to compute, and displays the reply. A client-side calculator receives the page once, then computes the answer on your device as you type. The result is the same number, but the route differs, and so does the question of who sees your inputs along the way.

The same idea extends beyond arithmetic. Modern browsers can also run compiled code through WebAssembly, which RedMonk described in January 2023 as a W3C standard designed to run executables on web pages portably, quickly and securely. That is a large part of why tasks that once needed installed software, such as resizing images or inspecting a 3D model, can now run in a browser tab.
Terms you will see in this topic
| Term | Plain meaning |
|---|---|
| Client-side | Work done on your device, usually in the browser |
| Server-side | Work done on a remote computer run by the site’s operator |
| Local file processing | A file is opened and changed in your browser without being uploaded |
| Offline-first | The tool keeps working after its first load, even without a connection |
| Zero egress | Your data does not leave your device |
The last two rows are often mixed up, so they get their own section below.
Offline-first and zero-egress are different properties
A 2026 arXiv paper on browser-based command-line tools, the Web-CLI study, separates the two ideas clearly. Offline-first means the application keeps working after its initial load without a connection. Zero-egress means user data does not leave the device. A tool can be one without the other: an app can work offline yet sync your content to a cloud account when a connection returns, and a tool can keep your data on the device while still needing a connection to load its page.

The same researchers argue that privacy can be enforced by architecture, through zero egress, instead of resting only on a provider’s promise not to retain uploaded data. That is the practical reason to prefer client-side tools for anything personal or confidential. A promise can be broken or changed in a later policy. A design in which the file never leaves your machine leaves nothing to promise.
For documents, the same logic applies to storage. Encrypting data before it reaches cloud storage, as covered in a write-up on encrypting data in the cloud, is another way to reduce exposure. Local processing goes a step earlier: if nothing is uploaded, there is nothing in transit to protect.
We describe our own approach in more detail in Online Tools and Privacy: What Stays on Your Device.
Three ways to get a task done online
Most people finish a calculation or a file task one of three ways. They use a browser tool that runs locally, an online tool that uploads input to a server, or software installed on their computer. The comparison below uses the criteria that matter for everyday tasks.
| Criterion | Local browser tools (GizmoBench) | Upload-based online tools | Installed software |
|---|---|---|---|
| Where processing happens | On your device, in the browser | On the operator’s server | On your device, outside the browser |
| Account needed | No | Often | Depends on the product |
| Installation | None | None | Required |
| Files leave your device | No | Yes, for file tasks | No |
| Works on any computer with a browser | Yes | Yes | Only where installed |
| Large files | Supported, within your browser’s memory | Often capped by upload size and time | Limited by your hardware |
GizmoBench comes first here because it combines the strengths of the other two: the convenience of opening a page and starting, and the privacy of keeping everything on your own machine. Installed software is a reasonable route for specialist professional work, and we compare browser and desktop options for one such case in Large File Editor: Browser and Desktop Options Compared. For the common small and medium tasks in this article, a local browser tool covers the job without setup.
Well-known calculator collections such as Omni Calculator, calculator.net, and CalculatorSoup cover many of the same topics. The question to ask of any of them, and of any tool, is the one in the table: does your input stay on your device? Our positioning is that GizmoBench tools run locally with no uploads or accounts, which differs from most competitors that run server-side processing or require registration.
For a closer look at how local tools stack up against a specific upload-based file service, see Smallpdf Alternatives: Why Local Browser Tools Come First.
Which tool for which task
The catalog is organized around practical jobs. These are the tools most readers of this topic come looking for, grouped by what they are doing.
Everyday numbers
The everyday tools page collects the Unit Converter, Percentage Calculator, Age Calculator, Random Number Generator, Soil Calculator, Guitar Tuner, Image Resizer, Collage Maker, Text to Audio, and Password Generator.
- Converting measurements. The Unit Converter handles length, mass, temperature, volume, and more. It suits cooks converting a recipe and DIYers working from a plan written in another measurement system.
- Price comparisons. The Unit Rate Calculator works out price per unit in both directions, which is useful when two package sizes make a comparison hard.
- Splitting a bill. The Bill Split Calculator handles itemized orders, tax, and tip.
- Garden planning. The Soil Calculator, found on the everyday page, estimates how much soil a raised bed needs.
These are small inputs, such as a bill total or a bed’s dimensions, but a share of them is personal: pay, savings, and expenses are numbers many people prefer not to send anywhere.
Work and school
The work tools page lists the GPA Calculator, Invoice Generator, Resume Builder, and Hours Calculator.
- Invoicing. The Invoice Generator produces an invoice as a PDF without sign-up. Client names, amounts, and payment details are exactly the kind of data that benefits from staying on your device.
- Resumes. The Resume Builder keeps personal history, addresses, and phone numbers in your browser as you edit.
- Time and grades. The Hours Calculator and GPA Calculator turn schedules and course results into totals. Students and hourly workers can use them without creating an account.
Images and creative work
Image tasks are where local processing matters most, because photos carry personal detail.
- The Image Resizer resizes to exact pixels, by percent, or in batches. Variants exist for Instagram and for resizing without cropping.
- The Image Compressor compresses to a target size in KB or MB, handy when a form or email limits attachment size.
- The GIF Resizer resizes while keeping the animation.
- The Collage Maker builds photo collages in the browser, with layouts for wallpapers, Instagram, and Facebook covers.
- Photos also carry hidden metadata. Our three-step workflow to remove EXIF data locally shows how to clean that without uploading the image.
Music and sound
The Guitar Tuner lets you tune by ear with reference tones or with your microphone. There are dedicated pages for alternate tunings, including Drop D, Open D, Open C, and Whole Step Down. Text to Audio, on the everyday page, converts text into spoken audio.
Developer and technical work
The developer tools page holds the JSON Formatter and the Base64 Encoder & Decoder. Related pages include the Epoch Converter, the IEEE 754 Converter for inspecting Float32 and Float64 bits, the PX to REM Converter, the JavaScript Minifier, and the JavaScript playground for running code in the browser. Developers pasting tokens, payloads, or source code into a formatter have an obvious interest in that text staying on their machine.
For makers, the 3D tools page offers an STL Viewer and a 3MF to STL converter, and the Markdown page offers a Markdown Viewer. The Mouse Test checks a mouse’s buttons and movement, and the Online Notepad is a text editor that saves in your browser.
How local file processing works in practice
When you drop a file onto a local browser tool, the browser reads it from your disk into memory. The page’s own code then transforms it, for example by resizing pixels, reformatting text, or converting a 3D model, and hands the result back as a download. No network request carries the file anywhere, since the work never needs a server. That is the difference between local file processing and an upload-based converter, which must send your file out and bring a result back.
This design has a few consequences worth knowing.
- Speed depends on your device. The work uses your processor, not a server farm. The Web-CLI authors note that computationally intensive WebAssembly operations can be much slower than native processing, so a very heavy job on an older machine takes longer than a small one on a new laptop.
- Memory sets the ceiling. The same paper notes that browser memory limits can constrain large files. GizmoBench is built to handle large files in the browser, and on any client-side tool you get the most headroom by closing other heavy tabs before a big job.
- Results are yours immediately. With no upload or queue, a small task returns as soon as the computation finishes.
- No account means no history held for you. Nothing is stored in a profile, so save the output you need when you finish.
A worked example: invoicing a client privately
Suppose a freelancer needs to bill a client for 14.5 hours at $60 an hour, plus 8% sales tax. The arithmetic is $60 × 14.5 = $870, and 8% of $870 is $69.60, so the total is $939.60. That sum is trivial, but the invoice around it holds a client’s name, address, and payment instructions.
The routine:
- Work out the hours with the Hours Calculator if your time is spread over several days.
- Open the Invoice Generator and enter your details, the client’s details, and the line items.
- Check the totals against your own arithmetic. The numbers above are an illustration, and the tax rate that applies to you depends on your location and the nature of the work.
- Export the PDF and send it.
Throughout, the data stays in your browser. For tax questions, such as whether sales tax applies to your work, ask an accountant or your state’s tax authority, since a calculator cannot decide that for you.
Choosing a client-side tool: five criteria
Whether you use ours or another, a short list of questions separates a good client-side tool from a weak one.
- Where does the input go? The strongest design keeps data on the device, which is the zero-egress property described earlier.
- Is an account required? An account means a record tied to you. Our tools do not require one for their core functions.
- Does it need installation? A tool that runs in any modern browser works on a borrowed or locked-down computer.
- Does it state its inputs and assumptions? A good calculator shows what it assumed, so you can check the result.
- Does it handle your file size? Check the tool’s stated range before a large job.
On these points, GizmoBench’s design answers the first three directly. Core tool functions are free to use with no account, though we do not promise that every feature will stay free forever.
Where GizmoBench fits
GizmoBench is a growing collection of calculators, converters, generators, editors, viewers, checkers, and timers. Each runs in your browser, files are processed locally, and the catalog keeps expanding around practical tasks. If you want a single place for the everyday numbers, the work documents, the image jobs, and the technical utilities described above, start at the GizmoBench home page or browse the practical guides that walk through individual tools.
FAQ
What does client-side mean?
Client-side means the work happens on your own device, usually in the web browser, instead of on a remote server. Cloudflare notes that this code is almost always written in JavaScript. The client is you, and the server is the site’s operator.
Do client-side tools work without an internet connection?
Not automatically. A tool needs a connection to load its page the first time. Offline-first behavior, where the app keeps working after that first load, is a separate property from keeping data on your device, as the Web-CLI paper explains. Check each tool’s page for what it supports.
Are client-side tools more private than upload-based ones?
When the design keeps data on your device, there is no upload for anyone to retain, which is the architectural privacy the Web-CLI researchers describe as zero egress. GizmoBench tools run locally and do not transmit your files. For regulated or highly sensitive material, follow the rules set by your employer or the relevant authority.
Can a browser tool handle large files?
Yes, within the limits of your device. Browser memory is the main constraint, so closing other heavy tabs before a large job helps. GizmoBench is built for large-file compatibility, and our large file editor comparison goes into detail.
Do I need an account to use GizmoBench?
No. The core tool functions work without an account or any installation. Open the page for the task you need and start.
Sources
- What Do Client-Side and Server-Side Mean? (Cloudflare)
- Why You Should Pay Attention to WebAssembly (RedMonk, January 18, 2023)
- The Web-CLI: Verifiable Privacy for Tools, Models, and Agents (arXiv, 2026)