The bent arrow ↵, the abbreviations CR and LF, and the phrase “press Return” all come from the same history of moving to a new line. In modern text files, however, they refer to different layers.
A keyboard key can trigger an action. A visible arrow can label that action. A file can contain control characters that mark line endings. Mixing those layers is how people end up searching a document for ↵ when the data actually contains U+000A LINE FEED.
Start With the Three Identities
| Form | Unicode | Role |
|---|---|---|
| ↵ | U+21B5 DOWNWARDS ARROW WITH CORNER LEFTWARDS | Visible return/new-line style symbol |
| CR | U+000D CARRIAGE RETURN | Control character |
| LF | U+000A LINE FEED | Control character |
Unicode notes that ↵ may indicate a carriage return or a new line. The important part is that ↵ itself is a visible character in the Arrows block; CR and LF are control characters that normally have no printed glyph.
Why “Carriage Return” Has That Name
The names are mechanical because the operations originally were. Carriage return meant returning the writing position to the start of the line; line feed meant advancing to the next line. Electronic text systems kept those two controls even after the physical carriage was gone.
That history is why CR and LF can still be treated separately. A modern file may use one, both, or a convention defined by the surrounding system.
LF, CRLF, and Line Endings in Files
Today, line endings are commonly encountered in two forms: LF by itself, or the pair CRLF. Different operating systems and protocols developed different conventions, which is why a file can appear to have odd blank lines or one long line when opened by software that expects another convention.
This is a storage issue, not a keycap issue. The main Return or Enter key might cause an editor to create a line break, but the editor chooses how that break is represented in the file.
The earlier Enter vs Return distinction therefore belongs one layer above CR and LF. The key is input; the line-ending sequence is data.
What ␍ and ␊ Mean
When control characters need to be visible, Unicode provides control pictures.
- ␍ is U+240D SYMBOL FOR CARRIAGE RETURN.
- ␊ is U+240A SYMBOL FOR LINE FEED.
-  is U+2424 SYMBOL FOR NEWLINE, another visible notation for the idea of a newline.
These pictures are not the control characters themselves. A hex editor, terminal visualizer, or textbook may display ␍␊ to explain CRLF, while the underlying file contains the bytes/control codes corresponding to CR and LF rather than the visible U+240D and U+240A characters.
↵ Is Not a Hidden Line Ending
The symbol ↵ is often used in interfaces to mean Return, Enter, or a line break. That makes it tempting to search for U+21B5 when a document has line-ending problems.
Usually that is the wrong target. A file that uses LF does not need a literal ↵ at the end of every line. Editors can draw return-style arrows, dots for spaces, or arrows for tabs as a viewing aid without changing the stored text.
Unicode also contains ⏎ U+23CE RETURN SYMBOL, another keyboard-oriented representation. A return-style glyph in a menu is therefore not enough to identify the file’s line-ending convention.
Why Copying a Visible Marker Can Mislead You
Suppose an editor shows a visible ↵ at the end of each line. Copying the text may omit those markers because they belong to the editor’s display layer. In another tool, the same file may show “LF” badges, pilcrow-like marks, or nothing at all.
If you need to diagnose line endings, inspect the underlying bytes or code points rather than the decoration. That is especially important in source control, shell scripts, configuration files, CSV exports, and network protocols.
Why Line Endings Still Matter
Most modern editors hide line-ending details until something goes wrong, but they still surface in practical work. Version-control systems may report a file as changed after a line-ending conversion. A shell script transferred between systems may fail if a tool interprets an unexpected carriage return literally. Network protocols can prescribe CRLF even when the local editor normally saves LF.
None of those problems can be diagnosed from the Return key label. The useful evidence is the stored sequence. Editors therefore often show a status indicator such as “LF” or “CRLF” and provide a command to convert the whole file deliberately.
How to Read the Terms Without Mixing Them
Use Return/Enter when talking about the key or user action. Use CR, LF, or CRLF when talking about encoded line endings. Use ↵, ␍, or ␊ only when you specifically mean those visible symbols or when a diagram is using them as notation.
Once those layers are separated, a lot of line-ending confusion disappears. The same Return key can be mapped to different stored line endings because the application and environment decide how the action is encoded.
You see the same pattern elsewhere in keyboard notation: a printed symbol can name an action without describing the bytes or code points that software will eventually store.