Markdown Remove Empty Lines

Remove every blank line, keep code blocks intact

Markdown Remove Empty Lines deletes all blank lines from a Markdown document, except the ones inside fenced code blocks. A line counts as blank when it is empty or contains nothing but spaces or tabs. What you get back is a compact file where every remaining line has content, while code samples keep the spacing that makes them readable and, in some languages, valid.

This is a stronger operation than tidying. Many tools reduce several empty lines to one; this one removes them all. That has real consequences for how Markdown renders, explained in detail below, so it is worth knowing when it helps and when it hurts.

Where removing blank lines helps

• Lists of items, one per line. Link lists, keyword lists, glossary entries or tag lists copied from somewhere often arrive double spaced. Removing the gaps produces a tight list.
• Front matter and data-like Markdown. Some generated files have spacing that serves no purpose. Compacting them makes them easier to scan and diff.
• Text going into a single field. Forms, spreadsheet cells, chat inputs and some APIs treat every blank line as wasted space or even as a separator you do not want.
• Exports from rich text editors. Copying from a word processor or a web page frequently inserts an empty line after every paragraph or list item. If the target does not need them, this clears them in one step.
• Preparing text for line-based scripts. When each line is processed as a record, blank lines are just noise.

Where it hurts: Markdown needs some blank lines

In Markdown a blank line is a structural signal. Removing all of them changes how many documents render:

Headings, fenced code blocks, horizontal rules and tables generally still render without blank lines around them, because they are recognised by their own syntax. Plain paragraphs are the main casualty. If your goal is a readable rendered page, consider Markdown Minifier instead, which keeps one blank line between blocks.

What happens inside code fences

The tool tracks fenced code blocks, which open with ``` or ~~~ (three or more, after any indentation). While it is inside one, every line, blank or not, is copied unchanged. A block opened with backticks is only closed by another backtick fence, and a tilde block only by a tilde fence. Blank lines inside a function, between paragraphs of a shell heredoc, or in a YAML sample therefore survive.

The sample text you can load into the tool shows this: it has blank lines around a paragraph that are removed, and a blank line inside a JavaScript function that stays.

Runs in the browser

The cleaning happens in JavaScript on this page. Your text is not uploaded and no request goes to a server. You can use it on unpublished drafts or internal documents without them leaving your machine.

How to use it

1. Paste Markdown into the Input Markdown editor, type it, or click Paste. Click Load sample if you want to try it on a short example first.
2. Click Remove Empty Lines in the header, or Remove below the editor.
3. The result appears in Clean Output, with any blank space at the very start and end trimmed off.
4. Read the counters at the top: Input lines, Output lines and Removed, which is the difference between the two.
5. Click Copy or Download. The download is named markdown-no-empty-lines.md.
6. Use Clear to start again.

Worked example

Input with gaps:

- Apples
(blank)
- Pears
(blank)
(blank)
- Plums

Output:

- Apples
- Pears
- Plums

Input lines 6, output lines 3, removed 3. A rendered loose list with spaced items has become a compact tight list.

Tips

• Check paragraphs after cleaning. If two paragraphs merged and that matters, add a single blank line back between them, or end the first with a backslash to force a line break.
• Close every fence. If a fence is opened and never closed, the tool treats the rest of the document as code and keeps all its blank lines.
• Normalise first for mixed sources. Windows line endings are handled, but if text came from very old Mac software with lone CR endings, run Markdown Normalize Line Breaks first.

Choosing the right blank-line tool

Three tools in this family touch blank lines, each in a different way. This one removes every blank line outside code fences and leaves everything else on each line alone. Markdown Minifier keeps a single blank line between blocks, so paragraphs stay separate, and also trims trailing spaces; it runs on the server. Markdown Remove Code Blocks collapses the gaps left behind when it deletes code, again keeping one blank line. If you are unsure, start with the minifier: it is the gentler option and almost never changes how a document renders. Choose this tool when you specifically want no gaps at all, typically for lists, data-like files and text going into fields that treat blank lines as noise.

What not to do

• Do not use it on long-form articles meant to be rendered, unless you plan to put paragraph breaks back.
• Do not expect it to trim spaces inside lines or at their ends. Lines with content are kept exactly; only whole blank lines are removed.
• Do not use it to remove blank lines from code samples. Those are deliberately protected.

Limitations

• All blank lines outside fences are removed; there is no option to keep one between blocks.
• Indented code blocks (four spaces, no fence) are not protected. Blank lines between their lines are removed, which can split or merge them.
• Blank lines inside HTML blocks are removed as well, which can change how some HTML in Markdown is parsed.
• No size limit is set in code; very large documents depend on your browser's memory.

Frequently Asked Questions