JSON Size Calculator — Bytes Before and After Minify
Measure UTF-8 byte size of your JSON as pasted and after minification to compare footprint.
How it works
- 1Paste or type your text in the input field
- 2Click "Calculate size" — processing happens in your browser
- 3Copy the result or download as a text file
What to do next
About JSON Size Calculator
JSON Size Calculator is a free, in-browser developer tool. Measure UTF-8 byte size of your JSON as pasted and after minification to compare footprint. The page exposes a small surface — input, controls, output — so a first-time visitor can complete the job without reading documentation.
The processing pipeline is straightforward: your input is parsed by standard browser APIs, transformed according to the options you select, and serialised back into a downloadable result. The 0 MB per-file ceiling matches what a typical browser tab can handle without paging to disk.
JSON Size Calculator is shaped for the gap between "I'll do it by hand" and "I'll script it." When the job is small enough that automating it would take longer than doing it, but annoying enough to want a focused tool — that is the situation this page is built for.
JSON Size Calculator is structured so the question "where is my file processed?" has a single answer: in your browser tab. The engine, the controls, and the result panel are all on one page. Navigating away or closing the tab clears the page's memory the way it does for every other tab.
The 0 MB ceiling on input size is the only fixed limit. Output files are produced in standard formats that every common viewer recognises, and the tool runs the same way regardless of how many times you have used it during the session.
Once you have used JSON Size Calculator, the natural next steps depend on what you are doing with the result. Common follow-ups include JSON Minifier, JSON Validator, and JSON Viewer / Formatter. These are surfaced on the page so you do not have to hunt the catalog manually.
JSON Size Calculator is shaped around the recurring needs of two audiences: students learning new languages, who use it as a quick utility between bigger tools, and backend developers inspecting requests, who use it as their primary way of getting the job done. Both groups get the same defaults and the same speed.
Output handling is intentionally boring: JSON Size Calculator produces a single output file and triggers your browser's standard "save" behaviour. If you have a default download folder configured, that is where it will land. There is no Favtoo-side history of jobs you have run.
Some notes on the design of JSON Size Calculator. The page is intentionally narrow: one input, the controls relevant to the task, and one output. Adding unrelated features would make the common case slower for the majority of users, so the surface is held to what people actually use.
JSON Size Calculator is one example of a broader pattern: utility software increasingly works as single-page, client-side experiences. Every page in the catalog is shaped that way, which keeps each tool fast to load and easy to recommend in a single link.
Useful patterns when working with JSON Size Calculator: keep the input file open in another tab so you can compare against the result; give the output file a descriptive name when saving so you can find it later (the default name is sensible but generic); and treat each run as independent — the tool has no concept of "history", which means you cannot accidentally pollute one job with leftovers from another.
JSON Size Calculator is built around the moment of need: a focused page you open when you have a specific task, complete the task, and close. The catalog contains many adjacent tools so the same model serves the surrounding parts of a typical developer utility workflow.
Common gotchas worth flagging: the supported formats are listed in the upload area. The 0 MB ceiling is per-file, not per-session; you can run as many separate jobs as you like, but a single oversized input will be rejected on load.
That is the whole tool. Use JSON Size Calculator for as long as it stays useful to you, and if it does, the catalog has many more tools built the same way. Each applies the same single-purpose discipline, so the way you used this page transfers to the next one you try.
How it works
- 1Land on the JSON Size Calculator page. The tool is ready to use the moment the page renders.
- 2Add your developer input by dropping it onto the page or browsing for it.
- 3Tweak the controls if the defaults are not quite right for your input. The options are kept short and labelled in plain language.
- 4Trigger processing. standard browser APIs reads your input, applies the transformation, and writes the result back into the page.
- 5Save the output when it is ready.
- 6Re-run with different settings as often as you want. Each run produces a fresh output and the original file on disk is never modified.
Common use cases
- Hash a string for a quick reproducibility check using JSON Size Calculator.
- Generate boilerplate from a single specification line.
- Inspect a regex against a test string before committing it.
- Convert between data formats while wiring up an integration.
- Decode a token to confirm its claims during a debugging session.
- Format a noisy log line into something a teammate can read.
- Generate a quick fixture without leaving the browser.
- Pretty-print a minified blob during incident triage.
- Encode binary content for transport in a JSON body.
FAQ
How are bytes measured?
TextEncoder encodes the UTF-8 bytes of your input string and of the minified JSON string separately.
Why is minified size smaller?
Minification removes whitespace between tokens, which can significantly shrink pretty-printed developer JSON.
Does gzip compression show?
No — only raw UTF-8 sizes are reported; gzip ratios need a compression tool or server metrics.
Is measurement local?
Yes — all counting happens in your browser without uploading the document.
What if JSON is invalid?
Minified size requires JSON.parse; invalid input surfaces the parse error instead of stats.
Are BOM characters counted?
Yes — any hidden characters in your paste contribute to the UTF-8 byte length.
Are there any hidden fees with JSON Size Calculator?
JSON Size Calculator is free to use. The processing runs in your browser, which keeps the per-user cost low enough that the tool can be offered openly. The download is the same file the engine produced — you can use it for as many runs as you need.
Can I use JSON Size Calculator for commercial work?
JSON Size Calculator can be used for personal and commercial work alike — there is no separate "business" licence to purchase. The output you generate is yours to use however you want, including in client deliverables, internal documents, or commercial products. Favtoo's only ask is fair, individual use; the tool is not designed to be embedded as a backend service or wrapped behind an API for resale.
Can JSON Size Calculator run inside a corporate firewall?
JSON Size Calculator is a static page running an open-source engine in your browser, so a typical corporate firewall does not get in the way as long as it allows JavaScript to load from Favtoo. For teams that need to host it themselves on an internal network, the underlying engine (standard browser APIs) is open-source and can be packaged into a private build with the same behaviour. Reach out via the Contact page if that is something you are exploring.
Are jobs run with JSON Size Calculator stored anywhere?
Favtoo keeps no copy of your file because Favtoo never receives your file. JSON Size Calculator runs entirely in your browser, the input is held only in your tab's memory, and closing the tab discards it. There is no opt-in cloud history, no "recent jobs" panel synced to an account, and no server-side retention to configure — the architecture simply has nowhere for your file to be stored.
What does JSON Size Calculator do that command-line tools do not?
Desktop apps usually have more advanced features but require installation, maintenance and (often) a licence. Paid online tools are convenient but route your file through their servers and gate downloads behind accounts. JSON Size Calculator sits in between: free, instant, and private, but intentionally narrow in scope. For one-off jobs and the common developer utility operations, it is usually the lowest-friction choice; for highly specialised work, a dedicated app is still the right answer.
Is JSON Size Calculator mobile-friendly?
JSON Size Calculator runs in any modern mobile browser — Safari, Chrome, Firefox and the in-app browsers in most messaging apps all support the underlying APIs. Performance depends on the device: a recent phone handles typical inputs nearly as fast as a laptop, while older devices may take a few seconds longer near the 0 MB ceiling. The interface lays out cleanly on small screens, so you do not need to pinch-zoom to see the controls.
How long does JSON Size Calculator take to process a file?
Most jobs finish in seconds. Speed scales with input size and with how many CPU cycles your browser tab has available — the engine runs in your browser, so it shares resources with whatever else you have open. For inputs near the 0 MB ceiling, expect anywhere from a few seconds to roughly a minute on a typical laptop. Closing other heavy tabs noticeably speeds things up.
Which browsers are supported by JSON Size Calculator?
JSON Size Calculator works in any modern browser released in the last few years — Chrome, Edge, Firefox, Safari, Brave, Arc and the major Chromium derivatives are all supported. The underlying engine relies on widely-supported web APIs, so there is nothing exotic to install. If you are on a very old browser version and the tool fails to load, updating to the latest release of your preferred browser is the only fix needed.