Hex Number Splitter

Break a single hexadecimal string into fixed-size chunks, reading left to right, with one chunk written per output line, useful for regrouping a long hex dump into bytes, words, or any other fixed-width grouping. A free online tool from Staaarter, right in your browser.

Runs locallyUpdated 2026-07-26

Overview

Introduction

Long hex strings, like memory dumps, hashes, or packed binary data rendered as text, are often easier to read or process once they're broken into consistent groups rather than left as one unbroken run of characters.

This tool takes a single hex value and cuts it into fixed-size chunks from left to right, printing one chunk per line so the result is easy to scan or paste into a script that expects one token per line.

What Is Hex Number Splitter?

The Hex Number Splitter is a simple regrouping tool: it doesn't change any digit's value, it only inserts line breaks at regular intervals through an otherwise unbroken hex string.

You control the interval with the chunk size field (default 2, meaning byte-sized groups), and the tool reads strictly left to right, so the grouping boundaries always start from the beginning of the string.

How Hex Number Splitter Works

The input is validated as a single hex string (an optional 0x/0X prefix is stripped first), then its digits are sliced into consecutive substrings of the requested chunk size, starting at index 0.

Each slice becomes one line of output; if the total digit count doesn't divide evenly by the chunk size, the last line simply contains whatever digits are left over, shorter than the rest.

When To Use Hex Number Splitter

Reach for this tool when you have one long hex string and need it regrouped into fixed-width pieces, for example turning a continuous hash digest into byte pairs, or a packed register value into nibble or word-sized pieces for inspection.

It's not the right tool if you already have multiple separate hex values and want to process each independently, most of the other list-based tools in this category, from the sorter to the incrementer, are built for that case instead.

Features

Advantages

  • Purely a formatting operation: no digit values are altered, only line breaks are inserted.
  • Handles uneven lengths gracefully by shortening only the final chunk, rather than erroring or padding.
  • Any positive chunk size works, not just byte-sized (2-digit) groupings.

Limitations

  • Only operates on a single hex string; to split many pieces from a list, run each one through separately or use a text tool to join/split beforehand.
  • Chunking always starts from the left edge; there's no option to align chunk boundaries from the right.

Examples

Splitting into byte-sized (2-digit) chunks

Input

1A2B3C4D5E6F, chunk size: 2

Output

1A
2B
3C
4D
5E
6F

The 12-digit input divides evenly into six 2-digit chunks.

An uneven length with a 3-digit chunk size

Input

1A2B3, chunk size: 3

Output

1A2
B3

5 digits don't divide evenly by 3, so the final chunk ("B3") is only 2 digits long.

Best Practices & Notes

Best Practices

  • Use a chunk size of 2 when you specifically want byte-aligned groupings of a hex dump.
  • Pair this tool with Hex Value Padder first if you need every chunk to come out the same width regardless of the input's total length.

Developer Notes

Implemented as a simple left-to-right `String.prototype.slice` loop over the validated, prefix-stripped digit string; no rounding or padding logic is applied to the final chunk, so its length is whatever remains.

Hex Number Splitter Use Cases

  • Regrouping a continuous hash digest or memory dump into byte pairs for readability
  • Splitting a packed register or bitfield value into nibble- or word-sized pieces
  • Preparing one-token-per-line input for another list-based hex tool in this category

Common Mistakes

  • Expecting the last chunk to be padded to full width; it isn't, by design, so it can be shorter than the others.
  • Forgetting that a 0x prefix on the input is stripped automatically, then being confused that the digit count (and therefore the chunk boundaries) doesn't include it.

Tips

  • If you need every output chunk padded to the same width, run the output through Hex Value Padder afterward.
  • A chunk size of 4 is a quick way to see a hex string regrouped into 16-bit words instead of bytes.

References

Frequently Asked Questions