Newline (line break)

Characteristics and encodings

The most common encodings are the line feed (LF) and carriage return (CR). In ASCII and Unicode these are U+000A (LF) and U+000D (CR). LF is sometimes called line feed because it advances the paper one line in mechanical printers. CR is short for carriage return, originally returning the print head to the left margin. Some systems combine both characters in the sequence CR+LF (written CRLF) to perform both actions.

• LF alone: used by modern Unix-like systems (illustrated in many programming languages by the escape \n).
• CRLF: historically used by Microsoft Windows and in many Internet text-based protocols.
• CR alone: used by older classic Mac OS versions; modern macOS uses LF like Unix.
• Unicode also defines U+2028 (LINE SEPARATOR) and U+2029 (PARAGRAPH SEPARATOR) for unambiguous line/paragraph breaks.

History and origin

The distinction between CR and LF comes from mechanical typewriters and teletypes. A typewriter required two actions to start a new printed line: returning the carriage to the left margin and advancing the paper one line. Early teleprinter equipment and terminal protocols retained that split behavior, which carried into early computer character standards. Over time different platforms adopted different conventions, producing the variety seen today.

Uses, examples and practical effects

In programming, the newline influences string literals, file contents, and text rendering. Many languages use the escape sequence \n to represent a newline (typically LF). Network and Internet protocols such as SMTP and HTTP specify CRLF as the end-of-line marker in header and protocol lines. When transferring files between systems with different conventions, mismatched newline sequences can cause display or processing issues, diffs in version control, or problems with scripts that expect a particular form.

Handling and normalization

Text editors, version-control systems and libraries often provide newline normalization: converting various newline representations to a chosen internal form to avoid spurious differences. When interoperating with external systems, applications should be explicit about which newline convention they accept and produce. For display purposes, graphical environments usually render any newline sequence as a line break, while some text-processing tools treat Unicode line/paragraph separators differently from ASCII control characters.

Notable distinctions

• Logical newline versus physical device action: the concept can map to different low-level characters depending on platform.
• Protocol requirements: some standards mandate CRLF and will reject lines terminated by only LF.
• Human factors: inconsistent newline handling is a common source of bugs when moving text between systems.

Understanding newline conventions is essential for reliable text processing, cross-platform software, and network communication. Tools and libraries that normalize or explicitly control line endings reduce interoperability problems and make behavior predictable across environments.