Bullets made from real Unicode characters, not a list style, so they paste into Instagram, LinkedIn and Notion without collapsing back into plain lines.
When you make a bulleted list in a word processor, the bullets are not in the text. They are a paragraph style, drawn by the application, and they exist only as long as the document does. Paste that list into an Instagram bio, a Discord message or a plain-text field and the bullets vanish, leaving a stack of unmarked lines. The fix is to use a real character. The bullet, en dash, square and check marks this tool inserts are ordinary Unicode characters that live in the text itself, so they travel with it into any field that accepts text at all.
Splitting by line is the obvious case: you already have a stacked list and you want each row marked. Splitting by sentence is for turning a paragraph into a scannable list, which is a genuinely useful editing move when a block of prose is really a set of steps. Splitting on commas handles the pattern where a list was typed inline as a single run. The hyphen option produces markdown-compatible bullets, which is what you want when the destination renders markdown and would otherwise show your Unicode bullet alongside its own.
Because they were a paragraph style, not text. The bullets here are real characters stored in the text, so they survive a paste into any plain-text field.
The hyphen. Markdown renderers turn a leading hyphen into their own bullet, whereas a Unicode bullet would be shown literally alongside it.
The bullet, en dash and check mark are in very widely supported blocks and render everywhere in practice. Rarer decorative marks can vary more between platforms.