Frequently asked questions

Syntax errors, with the line and column where JSON.parse stopped. It reports the first error only.

JSON does not distinguish 1 from 1.0. Formatting re-serialises the parsed value, so number formatting and duplicate keys collapse.

Files of a few megabytes work in the tab; much larger documents can be slow on phones with limited memory.

No. It is a reversible encoding. Anyone can decode it, so never use it to protect a secret.

Text is encoded as UTF-8 bytes before Base64, and decoded back as UTF-8, so non-ASCII characters round-trip correctly.

This version handles text only. Binary files would need a file encoder, which is not part of this page.

Component for a single query value, where / ? & = must be escaped. Full URL keeps those separators intact.

Percent-encoding represents a space as %20. The + form belongs to HTML form encoding, not URLs.

decodeURIComponent does not treat + as a space. Replace + with a space first if the value came from a form submission.

Input encoding. This tool hashes UTF-8 bytes; tools that use Latin-1 produce a different digest for the same visible text.

SHA-256 or stronger for anything security-related. MD5 and SHA-1 are broken for collision resistance.

No. These are plain digests. For passwords use a dedicated algorithm such as Argon2 or bcrypt with a salt.

No. It removes comments and redundant whitespace. Unused-rule detection needs a full page audit.

Spaces around + and - inside calc() are required by the CSS specification. Re-test the stylesheet after minifying.

No. It expects plain CSS; preprocessors have their own build steps.

Version 4 UUIDs carry 122 random bits, so a collision is practically impossible for normal use.

v4 is random and not sortable. If you need sortable identifiers, use UUID v7 or ULID.

The page caps each batch at 100 to keep the tab responsive. Generate again for more.

No. It only decodes the token. Never treat the decoded claims as trusted without verifying the signature server-side.

Check the exp claim against the current time; clock skew between machines is a common cause of rejected tokens.

Prefer test tokens. Decoding happens locally, but a token is still a credential once it leaves your clipboard.

It formats common SELECT, INSERT, UPDATE and DELETE statements and upper-cases the usual keywords. It is not a full parser for every dialect.

Only whitespace and keyword case change. Always re-run a formatted query against a test database first.

No. It is a readability formatter, not a linter or a validator.

Characters are Unicode code points; bytes are the UTF-8 size, which is what most databases and limits count.

Many emoji are made of several code points (for example a base character plus modifiers), and each one counts.

Characters include spaces and line breaks. A separate count shows characters without spaces.

Words are lowercased before joining, so acronyms become normal words. Check identifiers that rely on capitalisation.

Case mapping is language-independent. Turkish dotted i, for example, may need manual correction.

Yes. Paste only the selection you want to transform.

Values with 11 or more digits are treated as milliseconds; shorter values as seconds. The page states which it used.

Yes. A timestamp of 0 resolves to 1 January 1970, 00:00 UTC.

Local output uses your browser time zone, including daylight saving rules for that date.

Temperature scales have different zero points, so conversion is an offset plus a factor, not a simple ratio.

Standard defined factors are used, with display rounding to six decimals. Repeated conversions can accumulate display rounding.

Lower L/100 km is better, while higher mpg is better, so the scales are inversely related rather than proportional.

Yes. The browser IANA time zone database supplies the offset for the selected date, including DST rules.

Common IANA zones are listed. Very new or renamed zones depend on the browser database version.

No. You choose the source zone explicitly; the result is formatted in the target zone.

Calendar arithmetic from the selected date: whole years, then months, then days, plus total days and the next birthday.

The date arithmetic uses the real calendar, so 29 February is handled without special input.

The tool refuses it, because an age cannot be negative.

Values are clamped to 0-255 and rounded, then written as uppercase HEX. Some tools keep lowercase or invalid input.

An alternative representation: hue in degrees, saturation and lightness in percent. It is useful for adjusting colours.

No. This converts colour formats; contrast checking is a different tool.

Where the browser supports the native eyedropper, yes. Otherwise use the colour input swatch.

HEX, an RGB triplet and a CSS custom property you can paste into a stylesheet.

No. The value exists only in the page until you close it.

X/100 × Y, X/Y × 100, and (Y − X)/|X| × 100 for change. Each formula is shown next to the result.

A decrease produces a negative percentage. The sign shows direction, not an error.

Displayed to four decimal places; the calculation itself is not rounded between steps.

No. It is a screening number. Muscle mass, age, sex and body composition are not part of the formula.

Switching cm/kg to in/lb converts the height and weight values, so the same person keeps the same BMI.

The standard WHO screening bands: under 18.5, 18.5-24.9, 25-29.9 and 30 or above.

They are created with the browser crypto generator. Store them in a password manager rather than memorising or reusing them.

The page estimates bits of entropy from length and character sets. Longer passwords add more entropy than extra symbols.

No. Generation happens in the tab and nothing is stored or transmitted.

It is the classical lorem ipsum filler text used by designers, not running prose with meaning.

The output is plain paragraphs. Copy them into your layout and wrap them in the markup you need.

Placeholder text is generated on request so the page does not put filler in front of you unasked.

At 200 words per minute, rounded to whole minutes. It is an estimate for average reading speed.

Words are split on whitespace, so hyphenated compounds count as one word unless spaces separate them.

Yes. Words, characters, sentences, paragraphs and reading time are shown together.

Distance converted to kilometres, multiplied by consumption in L/100 km, then by the fuel price. A round trip doubles the distance.

L/100 km, km/L, mpg (US) and mpg (UK). The inverse conversions follow the standard formulas.

None. The result is a plain amount based on the price you enter, so any currency works.