Text ↔ binary

Client

Convert UTF-8 text to bit strings and back—hex view on hex encode.

About Text ↔ binary

Convert UTF-8 text to 0/1 bit strings and back—spaced bytes or continuous—in your browser. The interactive transform on this page runs in your browser tab—Toolcore does not need your paste for the core operation described above.

How to use this page

Paste or type in the main workspace, run the primary action from the toolbar, then copy or download the result. Use Load example when the page offers it, or URL prefill (?q= / ?qb=) so agents and tickets open the same input.

UTF-8 text ↔ raw bit strings—see byte view on hex encode or the encoding hub.

Plain text

?

Encoding uses UTF-8 bytes, eight bits per byte. Decoding strips anything that is not 0 or 1, then requires a full byte multiple.

Output

Nearby workflows on Toolcore

  • Hex encode & decode — UTF-8 text to hex and hex to text—strip spaces, local only. when the payload needs a different encoding or escape format.
  • Encoding tools — Hub index: Base64 & URL, Base64url, Base32, Crockford, LEB128, ASCII85, Z85, Base58, base-36, bencode, Morse, quoted-printable, URI, Puny… when the payload needs a different encoding or escape format.
  • Morse code encode & decode — International (ITU-style) Morse for Latin, digits, punctuation—. when the payload needs a different encoding or escape format.
  • File hex viewer — Hex dump the first 256 KB of any file with ASCII sidebar—read locally, no upload. when the payload needs a different encoding or escape format.

Common use cases

  • Explain how UTF-8 bytes look in binary for teaching or documentation.
  • Decode spaced bit dumps from lab exercises without a desktop tool.
  • Quickly verify a bit pattern before moving to hex or Base64 encoders.

Common mistakes to avoid

  • Treating bits as encrypted

    Binary encoding is reversible and not secrecy—use the crypto tools for protection.

  • Wrong bit grouping

    Decoding requires a multiple of eight bits after stripping separators.

FAQ

Which encoding?

Always UTF-8 bytes—ASCII is a subset; emoji and accents use multiple bytes.

Spaces in the binary input?

Ignored on decode—only 0 and 1 digits count toward bytes.

More tools

Related utilities you can open in another tab—mostly client-side.