What format does the binary input need to be in?

Space-separated 8-bit bytes, e.g. "11000001 11000010" — each group must be exactly eight 0s and 1s. Bytes that aren't exactly 8 bits, or contain anything other than 0/1, are rejected with a clear position-specific error.

What if a byte doesn't correspond to any printable character?

The tool reports exactly which byte (shown in both binary and hex) at which position isn't covered, since the CP037 table used here only maps printable ASCII (32-126) — not the full 256 possible byte values.

How is this different from the EBCDIC to ASCII Converter?

The EBCDIC to ASCII Converter (ascii category) expects each byte as 2-digit hex (e.g. C1); this tool expects the same byte as 8-bit binary (e.g. 11000001) — both use the identical CP037 lookup table underneath.

Can this decode raw mainframe file dumps?

Only if the dump's bytes are already presented as space-separated 8-bit binary and fall within CP037's printable range; this is a teaching/verification tool, not a general-purpose mainframe file converter.

Binary to EBCDIC Converter - CP037 Binary to Text

Overview

Introduction

Once text has been encoded as EBCDIC binary, recovering the original characters means running the CP037 mapping in reverse, byte by byte.

This tool does exactly that, decoding space-separated 8-bit EBCDIC bytes back into readable text using the same table this site's other EBCDIC tools share.

What Is Binary to EBCDIC Converter?

A decoder that reads 8-bit binary bytes and maps each one, via the IBM EBCDIC CP037 code page, back to its ASCII character.

It's the exact inverse of the EBCDIC to Binary Converter, and shares its lookup table with the ascii category's hex-based EBCDIC converters.

How Binary to EBCDIC Converter Works

The input is split on whitespace into individual byte groups, each validated as exactly 8 binary digits.

Each byte is converted to a 2-digit hex string with `parseInt(group, 2).toString(16)`, then looked up in a reverse map built from the same [character, hex byte] table the ASCII to EBCDIC Converter defines, recovering the original character.

When To Use Binary to EBCDIC Converter

Use it to decode EBCDIC binary data recovered from a legacy mainframe file, COBOL data dump, or protocol trace.

It's also useful for verifying a manual EBCDIC decoding exercise or confirming the EBCDIC to Binary Converter's output round-trips correctly.

Often used alongside EBCDIC to Binary Converter and EBCDIC to ASCII Converter.

Features

Advantages

Shares its byte table with the ASCII category's EBCDIC converters, so results stay consistent across the whole site.
Validates byte length and binary format strictly, with a specific, position-referenced error message.
Fast, fully client-side decoding.

Limitations

Only covers printable ASCII (32-126) in the CP037 table; bytes for control characters or unmapped code points return an error rather than a best-effort guess.
Only supports CP037 — bytes from other EBCDIC code pages (e.g. CP500, CP1047) may decode to different characters or fail entirely.

Examples

A short word

Input

11001000 11000101 11010011 11010011 11010110

Output

HELLO

The bytes 11001000, 11000101, 11010011, 11010011, and 11010110 (hex C8, C5, D3, D3, D6) map to H, E, L, L, and O respectively.

A single byte

Input

11000001

Output

11000001 in binary is 193 decimal (hex C1), which the CP037 table maps to the letter "A".

Best Practices & Notes

Best Practices

Keep bytes space-separated and exactly 8 digits each — the tool won't try to auto-split an unspaced binary blob into bytes for you.
Cross-check unfamiliar byte values against the CP037 reference table if the tool reports an unmapped byte.

Developer Notes

Builds a reverse `Map<hexByte, character>` from the ascii category's shared `ASCII_TO_CP037` array at module load, then validates each whitespace-split group with the category's `isValidBinaryString` helper before converting via `parseInt(group, 2).toString(16)`.

Binary to EBCDIC Converter Use Cases

Decoding EBCDIC binary data recovered from legacy mainframe systems
Verifying a manual EBCDIC-to-text decoding exercise
Confirming a round trip through the EBCDIC to Binary Converter

Common Mistakes

Running unspaced binary through this tool — bytes must be space-separated so the parser knows where each 8-bit group starts and ends.
Expecting every possible byte value to decode — only CP037's printable-ASCII range (32-126) is covered.

Tips

Pair this with the EBCDIC to Binary Converter to explore round trips on your own text.
If you already have EBCDIC bytes as hex instead of binary, use the EBCDIC to ASCII Converter (ascii category) directly instead of converting hex to binary first.

Binary to EBCDIC Converter