SPLIT(1POSIX)

🌸 SPLIT(1POSIX) 🌸

okay bestie, gather round, we're doing the POSIX Programmer's Manual today and honestly? this one's a bop. it's split, from the POSIX manual set (yes, the POSIX Programmer's Manual, that's the vibe we're on).

---

📢 PROLOG

This manual page is part of the POSIX Programmer's Manual. Heads up though: the Linux implementation of this interface may differ (so go check the corresponding Linux manual page for the deets on Linux behavior), or honestly the interface may not even be implemented on Linux at all. 💀 no cap.

---

✨ NAME

split — split a file into pieces

---

🎀 SYNOPSIS

split [-l line_count] [-a suffix_length] [file [name]]

split -b n[k|m] [-a suffix_length] [file [name]]

---

💖 DESCRIPTION

So split reads an input file and writes zero or more output files. cute, right? the default size of each output file is 1000 lines. you can change the size of the output files by specifying the -b or -l options. every single output file gets created with a unique suffix, and that suffix consists of exactly suffix_length lowercase letters from the POSIX locale. the letters of the suffix get used as if they were a base-26 digit system — like, the first suffix created is all 'a' characters, the second has a 'b' replacing the last 'a', and so on, all the way until a name of all 'z' characters is created. iconic counting behavior honestly. 🦋

By default, the names of the output files are 'x', followed by a two-character suffix from that character set we just described, starting with "aa", "ab", "ac", and so on, continuing until the suffix "zz" — for a maximum of 676 files. periodt.

If the number of files required exceeds the maximum allowed by the suffix length provided — like, such that the last allowable file would be larger than the requested size — split shall fail after creating the last file with a valid suffix. and here's the part bestie, listen: split shall not delete the files it created with valid suffixes. 🫶

If the file limit is not exceeded, the last file created contains the remainder of the input file, and may be smaller than the requested size. and if the input is an empty file? no output file shall be created, and this shall not be considered an error. (we love a chill empty-file moment.) 🌈

---

💅 OPTIONS

The split utility shall conform to the Base Definitions volume of POSIX.1‐2017, Section 12.2, Utility Syntax Guidelines.

The following options shall be supported:

• -a suffix_length — use suffix_length letters to form the suffix portion of the filenames of the split file. If -a is not specified, the default suffix length shall be two. If the sum of the name operand and the suffix_length option-argument would create a filename exceeding {NAME_MAX} bytes, an error shall result; split shall exit with a diagnostic message and no files shall be created. 🚫
• -b n — split a file into pieces n bytes in size.
• -b nk — split a file into pieces n*1024 bytes in size.
• -b nm — split a file into pieces n*1048576 bytes in size.
• -l line_count — specify the number of lines in each resulting file piece. the line_count argument is an unsigned decimal integer. the default is 1000. if the input does not end with a <newline>, the partial line shall be included in the last output file.

---

🍓 OPERANDS

The following operands shall be supported:

• file — the pathname of the ordinary file to be split. if no input file is given, or if file is '-', the standard input shall be used.
• name — the prefix to be used for each of the files resulting from the split operation. if no name argument is given, 'x' shall be used as the prefix of the output files. the combined length of the basename of prefix and suffix_length cannot exceed {NAME_MAX} bytes. see the OPTIONS section. 👀

---

🧚 STDIN

See the INPUT FILES section. (it's giving "go look up there", sorry bestie.)

---

🌸 INPUT FILES

Any file can be used as input.

---

💜 ENVIRONMENT VARIABLES

The following environment variables shall affect the execution of split:

• LANG — provide a default value for the internationalization variables that are unset or null. (See the Base Definitions volume of POSIX.1‐2017, Section 8.2, Internationalization Variables for the precedence of internationalization variables used to determine the values of locale categories.)
• LC_ALL — if set to a non-empty string value, override the values of all the other internationalization variables.
• LC_CTYPE — determine the locale for the interpretation of sequences of bytes of text data as characters (for example, single-byte as opposed to multi-byte characters in arguments and input files).
• LC_MESSAGES — determine the locale that should be used to affect the format and contents of diagnostic messages written to standard error.
• NLSPATH — determine the location of message catalogs for the processing of LC_MESSAGES.

---

⭐ ASYNCHRONOUS EVENTS

Default.

---

🎀 STDOUT

Not used.

---

🦋 STDERR

The standard error shall be used only for diagnostic messages.

---

🔥 OUTPUT FILES

The output files contain portions of the original input file; otherwise, unchanged.

---

👑 EXTENDED DESCRIPTION

None.

---

💀 EXIT STATUS

The following exit values shall be returned:

• 0 — successful completion. 🎉
• >0 — an error occurred. 😭

---

🌈 CONSEQUENCES OF ERRORS

Default.

The following sections are informative.

---

🙈 APPLICATION USAGE

None.

---

⭐ EXAMPLES

In the following examples foo is a text file that contains 5000 lines.

1. Create five files, xaa, xab, xac, xad, and xae:

split foo

2. Create five files, but the suffixed portion of the created files consists of three letters, xaaa, xaab, xaac, xaad, and xaae:

split -a 3 foo

3. Create three files with four-letter suffixes and a supplied prefix, bar_aaaa, bar_aaab, and bar_aaac:

split -a 4 -l 2000 foo bar_

4. Create as many files as are necessary to contain at most 20*1024 bytes, each with the default prefix of x and a five-letter suffix:

split -a 5 -b 20k foo

---

💅 RATIONALE

The -b option was added to provide a mechanism for splitting files other than by lines. while most uses of the -b option are for transmitting files over networks, some believed it would have additional uses. 📡

The -a option was added to overcome the limitation of being able to create only 676 files. (she needed range, she got range.)

Consideration was given to deleting this utility, using the rationale that the functionality provided by this utility is available via the csplit utility (see csplit). upon reconsideration of the purpose of the User Portability Utilities option, it was decided to retain both this utility and the csplit utility because users use both utilities and have historical expectations of their behavior. furthermore, the splitting on byte boundaries in split cannot be duplicated with the historical csplit. so she stays. 💅

The text ``split shall not delete the files it created with valid suffixes'' would normally be assumed, but since the related utility, csplit, does delete files under some circumstances, the historical behavior of split is made explicit to avoid misinterpretation.

Earlier versions of this standard allowed a -line_count option. this form is no longer specified by POSIX.1‐2008 but may be present in some implementations. 👀 (so don't come for me if you see it in the wild.)

---

🎀 FUTURE DIRECTIONS

None.

---

💖 SEE ALSO

csplit

The Base Definitions volume of POSIX.1‐2017, Chapter 8, Environment Variables, Section 12.2, Utility Syntax Guidelines

---

📜 COPYRIGHT

Portions of this text are reprinted and reproduced in electronic form from IEEE Std 1003.1-2017, Standard for Information Technology -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 7, 2018 Edition, Copyright (C) 2018 by the Institute of Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between this version and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained online at http://www.opengroup.org/unix/online.html .

Any typographical or formatting errors that appear in this page are most likely to have been introduced during the conversion of the source files to man page format. To report such errors, see https://www.kernel.org/doc/man-pages/reporting_bugs.html .

---

okay that's the whole page bestie, you ate that 🫶 this one came to you from IEEE/The Open Group, dated 2017, filed under SPLIT(1POSIX) — and that's the tea. 💖✨