One focused calculator

About Utf8ledger

Utf8ledger helps answer a specific question: how many UTF-8 payload bytes does this entered text require, and how does that compare with an explicit budget? It is useful when a byte limit matters and a simple visual character count gives the wrong impression. Accents, supplementary scalars and combining sequences make the differences visible.

The calculator keeps three units separate. UTF-8 bytes describe the encoded payload. UTF-16 units describe the received JavaScript string's encoding units. Unicode scalar values describe decoded code points outside the surrogate range. None is presented as a count of user-perceived characters or grapheme clusters.

Inspect the model

The tool does not normalize, trim or truncate your text. It counts an entered BOM and rejects an unpaired surrogate instead of measuring a replacement character. A paged scalar preview shows byte offsets, UTF-16 offsets, code-point labels and encoded bytes without filling the whole page with an unbounded table.

Editing either input clears the previous result and export state until you explicitly count again. Startup and reset use a fixed public example. Summary copy and downloads include every current total and the model, but not your pasted text or diagnostic rows. This makes the export scope clear rather than confusing one preview page with a complete data export.

Free use and scope

This independent website offers one free local calculator and its supporting guide, examples, privacy and contact pages. No account, payment or message is required to use it. This source release has no active advertising, analytics or consent-platform loader. Future setup and website publication are separate from actual visitors, ad serving or earnings.

The payload result is not a guarantee about a service's complete request, file or storage size. The guide explains the browser textarea newline boundary and what overhead is excluded. Optional feedback uses an existing shared public forwarding alias. An invented example is enough to report a discrepancy without exposing private text; the contact page explains how, and the privacy page describes local processing and separate browser actions.