Why a final newline makes two documents different

A file can display exactly the same words as another file and still differ at the end. One document may end immediately after the last visible character. The other may include a line feed after it.

Make the ending visible

Here is the difference using escaped strings:

const contentA = "release: ready";
const contentB = "release: ready\n";
contentA === contentB; // false

The \n represents a line feed, U+000A. This is a real character difference even though it adds no visible word. It is separate from adding a line containing additional text.

Inspect the example in Folio

Open the final-newline example

The Content A and Content B panes display the same text. Folio labels one ending No final newline and the other Final newline. This gives a visible explanation for the differing line instead of asking you to guess which character differs.

For your own documents, paste or open both documents, choose Plain text, and compare. Use Show whitespace to reveal line-break markers. Choose Unified if you prefer reviewing the Content A and Content B vertically, or Split to keep them next to each other.

Decide whether the difference matters

Check the consuming system or your project's conventions before removing or adding a final newline. A diff identifies a difference; it does not establish that either document is wrong. If you are reviewing an accidental formatting edit, verify that no other values differ.

In the example, choose Edit source and change “ready” to “pending” in one pane. Compare again. That visible text difference remains something to review independently from the ending.

A boundary to remember: normalized line endings

Folio normalizes CRLF and standalone CR line endings to LF before comparing source. It can show a missing final newline, but it is not a byte-for-byte file comparison tool and will not distinguish CRLF from LF in otherwise identical text.

Choose Plain text when you are investigating source characters. Normalized JSON removes indentation noise; choose JSON as entered to preserve the source layout. Plain text is the clearest choice for inspecting a final terminator. The exported comparison report is human-readable rather than an apply-ready patch.

Files are processed in your browser. Folio accepts UTF-8 text files up to 20 MB. Large source views display pages of 500 rows; search and export include the full content. Your document contents are not stored as history; export work you want to keep before reloading.

Reference: Unicode Basic Latin chart for the line-feed code point.