4629 · Encoding · v1.0.0

Encode

Text becomes a transportable signal.

Encode text as Base64, bytes, entities or language-specific escapes. Inspect the representation without sending your text to a server.

Processed locally in your browser

Representation

Text-only workspace. Never executes input. General limit: 200,000 UTF-16 units per editor; some operations have tighter limits.

INPUT14 UTF-16

OUTPUT0 UTF-16

Private session · history disabled

Opt in to store up to five recent text transformations on this device. Never stored on an account or synchronized. Files are never included. Disable history stops new saves; Clear history deletes saved items.

Enable local history for this session

How to use Encode

Paste input, select a command and its options, then run the transformation. Review diagnostics before copying or downloading the result. Input is not executed.

Byte encodings use UTF-8. UTF-16 output lists hexadecimal code units; UTF-32 lists hexadecimal Unicode scalar values. These are not byte-order-dependent file serializations. Malformed surrogate sequences are rejected rather than silently replaced.

Privacy and boundaries

Editor contents stay in your browser. Transformations run in a disposable worker and are never sent to a formatting or AI service. History starts disabled; enabling it writes text to local browser storage only. Clearing that history removes this tool’s saved entries, not data saved by other applications. The surrounding website may load its normal navigation and analytics, but the utility workspace is excluded from content-interaction capture.

Use the labeled operation selector for the available capabilities. Keyboard users can reach every control with Tab; Ctrl or Command plus K opens the command palette. Copy requires clipboard permission. Download creates a local text file. Clear removes the current workspace; it does not automatically delete an opted-in history. Inputs and outputs are always rendered as text, never as a runnable preview.

What is Base64 encoding?

Base64 represents three bytes with four ASCII symbols, adding padding when necessary. It is a transport encoding, not encryption.

FIELD GUIDE · PURPOSE AND BOUNDARIES

Encode: practical use and context

Encode turns text into explicit transport representations. It is for developers preparing payloads, students exploring character storage, and anyone diagnosing why the same text looks different when embedded in another format.

↑ Back to the application

A stream of cyan light particles passes through a glass prism and leaves as rows of binary-style light blocks — Application artwork reused from its publication image family. The interactive interface is above.

Purpose and practical uses

Choose this tool when a receiving system expects a particular representation, not when you want to keep information secret. Base64, hexadecimal and percent encoding are reversible descriptions of data. Someone who knows the format can recover the original. Useful tasks include preparing a small test fixture, documenting a byte sequence, and inspecting how accented text passes through a UTF-8 pipeline.

A deliberate workflow

Paste the exact text, including any intended spaces and line endings. Select the representation required by the next system and run Encode text. Inspect diagnostics and the entire result before copying it. Do not remove padding or alter letter case merely to make output look cleaner; characters that seem decorative can carry meaning in the chosen representation.

For a reversible workflow, copy the output into Decode and explicitly select the same format. Compare the recovered text with your original, preferably with a text diff when invisible characters matter. This tests a specific round trip. It does not prove that a third-party API accepts the result, because that API may require a different charset, padding convention or surrounding document structure.

A practical example

Use the built-in greeting containing an accented word and an emoji. Encode it once as Base64 and once as hexadecimal. The visible outputs differ, but both describe the same UTF-8 bytes. Then inspect the text with Unicode Explorer: a visible symbol, a Unicode code point and a byte are different units. This is a useful exercise before constructing multilingual fixtures.

Read the result correctly

UTF-16 output lists hexadecimal code units, while UTF-32 lists scalar values. Neither option silently supplies a binary file’s endianness or byte-order mark. Base64URL is intended for a different alphabet from conventional Base64. HTML entities and JSON string escapes solve syntax problems in those contexts; they are not interchangeable substitutes for a complete document serializer.

Limits and troubleshooting

Malformed surrogate sequences are rejected rather than silently rewritten. A different output after adding a trailing newline is expected, because the input changed. Keep tokens, passwords and confidential production payloads out of examples. The transformation runs locally, but clipboard history, browser extensions and anything you paste the result into have their own data handling. Encoding adds no access control.

Services

Company

Resources