Sometimes when you write markdown, you'll write some paragraph...
and then you hit "Enter" twice to make another paragraph.
Like this...
...and then this.
This will render:
<p>Like this...</p>
<p>...and then this.</p>
But, sometimes you want to make a single line break, kind of like in HTML where you have:
<p>
Like this... <br />
...and then this.
</p>
In markdown, you can just drop in a <br /> and it'll work perfectly fine. But, if you want to keep your markdown HTML-less, you can add a backslash \ after your line, like so!
Like this...\
...and then this.
This is supported in most markdown processors, but not all of them. Definitely check on the one you're using before you push to prod. Some processors also allow you to add a double space at the end of a line as well (truly just , hit your spacebar twice), but since a lot of code editor setups trim empty spaces, I personally prefer the backslash way.
Have
fun!
Top comments (5)
Well, on DEV, every line break in source is a line break in output, so basically each paragraph must be on a single line. And I must say I hate this, I much prefer one sentence per line (friendlier to Git diff'ing, as I publish on GitHub Pages for my own blog then copy/paste to DEV for reach).
DEV does support the double space one, though!
Oh no it's way worse!
without anything at the end of line, will turn into
I want it to be
And BTW, with the double space, it'll make two
<br>‼Nice!
The backslash recommendation has aged well: it is visible in review and survives formatters that trim trailing spaces. One portability detail worth adding is that CommonMark treats a plain newline as a soft break, but renderers may expose an option that turns soft breaks into
. I rechecked commonmark.js 0.31.2, markdown-it 15.0.0, and Marked 18.0.9 today: all three agree on backslash and two-space hard breaks, while markdown-it/Marked change plain newlines when breaks is enabled. So the safest production check is parser version + options, not only processor name.