Other properties
The Other properties page controls what the pieces contain besides your data: the format, a header or footer repeated in each piece, space kept free, and the identity of the set. The defaults suit most splits.
Find it in the navigation pane under Pieces.

Metadata and headers
Section titled “Metadata and headers”Piece format
Section titled “Piece format”| Choice | Effect |
|---|---|
| GSplit set (metadata: CRC-32 of each piece, SHA-256 of the file, GUnite, Self-Uniting) | The default. Each piece ends with metadata that lets GUnite check and rejoin the set. It also holds the set identity below. |
| Raw pieces (.001, .002 … — HJSplit, 7-Zip, Total Commander, copy /b, cat) | The pieces hold only your data. Other tools join them, and GUnite rejoins them as a raw set. The identity is not stored. |
Choosing raw pieces changes the default mask to {orf}.{oru}; choosing the GSplit set restores disk{num}.gsd. A mask you edited is kept. See File naming. For the byte layout of the metadata, see Piece format V4.
Write a Total Commander .crc checksum file
Section titled “Write a Total Commander .crc checksum file”Off by default, and available with raw pieces only. A GSplit set carries its own checksums.
Write a SHA-256 manifest (<name>.sha256)
Section titled “Write a SHA-256 manifest (<name>.sha256)”Off by default. Writes, once the pieces are complete, a text file with the SHA-256 of the pieces and of the original file. It is useful without GSplit: sha256sum -c and GUnite check it. Not available with disk-spanned pieces.
Write join scripts (.bat / .sh)
Section titled “Write join scripts (.bat / .sh)”Off by default. Writes a .bat and a .sh script next to the pieces that rebuild the file without GSplit: they call gunitec for a GSplit set and copy /b or cat for raw pieces. Not available with disk-spanned pieces, nor with Only create these pieces, since the scripts would rebuild an incomplete file.
Custom headers and repeated source lines
Repeat a header at the start of every piece but the first
Section titled “Repeat a header at the start of every piece but the first”Off by default. For CSV and log files, so each piece keeps the column names. Two ways to define the header:
- Header line typed in the field: the text is written in the encoding of the source file. Write a byte as
0xand two hex digits; end the line with0x0D0x0A(Windows) or0x0A(Unix). For UTF-16 and UTF-32 files, bytes written as0xHHare not converted. - The field left empty: GSplit repeats data taken from the source. With a pattern split, it is the data before the first occurrence of the pattern. In the other modes it is the first line of the file, or the number of lines set in Lines taken from the start of the file (at least 1).
Also at the start of the first piece is offered with a typed header; it needs a source without a byte order mark. In the lines mode, the page Type & size has a shortcut for the empty header: Repeat the first line (header) in every piece.
Add a footer
Add a footer at the end of every piece
Section titled “Add a footer at the end of every piece”Off by default. The Footer line is written at the end of every piece, the last one included, with the same byte syntax as the header. In a GSplit set, its length is recorded in the metadata so that the join skips it. In fixed-size mode the footer is taken from the piece size; in the lines and pattern modes it is added to the piece.
Text encoding: repeat the byte order mark
Start every piece but the first with the byte order mark
Section titled “Start every piece but the first with the byte order mark”Shown only when the source file starts with a byte order mark (UTF-8, UTF-16 or UTF-32). Off by default. Repeats the mark so each piece opens as text in the same encoding. In the lines mode on a UTF-16 or UTF-32 file, the mark is always repeated and the checkbox stays on.
Reserve space in the pieces
Reserved space
Section titled “Reserved space”Space left free in each piece, for example to add a readme file next to the first one. It is taken from the piece size. Both values are in bytes, 0 by default.
First piece (bytes)
Section titled “First piece (bytes)”Room kept free in piece 1.
Other pieces (bytes)
Section titled “Other pieces (bytes)”Room kept free in every other piece.
Add a title, author or description
Piece set identity
Section titled “Piece set identity”Stored in the piece metadata and shown by GUnite when it joins the pieces.
A title for the set.
Author
Section titled “Author”The author of the set.
Description
Section titled “Description”A free description.
Unique set ID
Section titled “Unique set ID”The identifier of the set, read-only. It is generated when the file is split. Generate draws a new one; the pieces of one set share it, which is how GUnite tells that pieces belong together.
