Short answer: There is no spoken command that creates a bullet. Start the list yourself with the app's list button or shortcut, dictate the first item, then say "new line" and keep talking. The editor adds each new bullet automatically, so you only ever create the list once.
Almost every dictation guide covers punctuation and capital letters. Almost none of them covers the thing people actually try on day two: talking a bulleted list into a document. You say "bullet point" and the words bullet point appear. You say "dash" and you get a hyphen floating in the middle of a sentence. You try "new bullet" and get exactly that, in plain text, mocking you from the page.
The reason this fails is not that your dictation is broken. It is that a bullet is not text. Understanding that one distinction turns lists from the most frustrating thing you can dictate into one of the easiest.
Why lists are hard for dictation
Dictation is a text-insertion system. It listens to your voice, decides what characters you meant, and drops those characters in at the cursor. Everything it can produce is a character: letters, digits, commas, quotation marks, line breaks. That is the full vocabulary of the thing.
A bulleted list is not a character. It is a document structure created and owned by the app you are typing into. When you click the bulleted list button in Apple Notes or Word or Google Docs, you are not typing a bullet glyph. You are telling the editor "the following block is a list," and the editor takes over from there: it draws the marker, it sets the indent, it hangs the text, and it decides what happens when you press Return.
That last part is the key that unlocks everything. Once a list exists, the editor already knows that pressing Return means "give me another item." So dictation never needs to know how to make a bullet. It only needs to know how to press Return, and it already does.
You do not dictate bullets. You dictate items, and let the editor keep the list going.
The method that works, in three steps
This works in essentially every rich text editor on Mac and iPhone, and it takes about five seconds to learn.
- Create the list once, by hand. Click the bulleted list button, or use the keyboard shortcut, or type
-(dash then space) in an app that auto-formats Markdown. You now have an empty first bullet with the cursor sitting in it. - Dictate the item. Say the whole item as one natural phrase. Do not say the word "bullet." Do not say "one." Just say the thing.
- Say "new line" and keep going. The editor closes that item and opens the next bullet for you. Dictate the next item. Repeat.
Spoken out loud, a five-item list sounds like this, in one continuous take:
"Confirm the venue deposit new line chase the catering headcount new line send the run of show to the AV team new line book the airport pickup new line draft the thank you note"
Five bullets. One breath group per item. Zero clicks after the first one.
Ending the list
When you are done, stop dictating and press Return twice, or press Return once and then Backspace. Both gestures tell the editor to exit list mode and return you to normal paragraph text. There is no reliable spoken command for "end the list," and trying to invent one is how people end up with the words end list as a sixth bullet.
New line versus new paragraph
Inside a list, these two commands do different things, and the difference matters more here than anywhere else in dictation.
- "New line" is a single line break. In most list editors this creates the next bullet, which is what you want.
- "New paragraph" is a harder break, often two line breaks. In some editors that ends the list entirely or leaves a blank bullet behind.
If your bullets keep coming out with gaps between them, or the list keeps terminating after every item, you are almost certainly saying "new paragraph" out of habit. Switch to "new line" and the behaviour usually snaps into place. We covered the full mechanics of both commands in how to dictate a new line and a new paragraph, including why the pause before and after the command matters.
Numbered lists
Numbered lists follow the same rule with one extra warning: do not say the numbers.
If you start an ordered list in the editor and then dictate "one, book the flight," you will get a bullet reading 1. 1. Book the flight or 1. one, book the flight, depending on how the app handles it. The editor is already numbering for you. Your job is only the words after the number.
So: create the numbered list, dictate the item text, say "new line," dictate the next item. The numbers appear on their own, they renumber if you reorder later, and you never have to think about them.
There is one case where you do want to say the numbers: plain text fields with no formatting, like a chat message or a code comment or a plain text note. There you are typing the numbers as literal characters, and the way you say a number determines how it comes out. "One" gets you the word, and a digit usually needs the numeral context to trigger. This is its own small science, and we walked through it in how to dictate numbers and dates correctly. In plain text, most people find it faster to dictate the items with "new line" between them and then add the numbering by hand, or skip numbering entirely and use dashes.
Nested and indented lists
Sub-bullets are where voice runs out of road, and it is worth being honest about that rather than pretending there is a trick.
Indenting is a Tab keypress. Outdenting is Shift-Tab. Neither has a spoken equivalent in built-in dictation on Mac or iPhone. There is no "indent" command that reliably fires, and the word will simply be typed.
The practical workaround is a two-phase workflow, and it is genuinely faster than trying to build the hierarchy live:
- Phase one, talk it flat. Dictate every item, parent and child alike, as a single flat list. Do not stop to think about structure. Do not reach for the keyboard.
- Phase two, structure it. Go back with the keyboard, click into the items that should be children, and hit Tab. Ten seconds of Tab presses beats two minutes of stopping and starting.
This split matters because the two activities use different parts of your brain. Generating content wants momentum. Arranging hierarchy wants a wide view of the whole list. Trying to do both at once is why so many dictated outlines come out shallow: people stop generating the moment they have to think about indentation, and the ideas that were queued up behind that thought never make it out.
Markdown editors: the dash-space shortcut
If you write in an editor that auto-formats Markdown, you get a shortcut that skips the list button entirely. Typing a hyphen followed by a space at the start of a line converts the line into a bullet automatically. Same for 1. and a space for a numbered list.
The catch is that dictating that hyphen is unreliable. Say "dash" or "hyphen" at the start of an empty line and you will often get a hyphen with a space in front of it, or the literal word, depending on the app and the language variant. Spoken symbols at the beginning of a line are the hardest case for the sentence engine to get right, which is a broader pattern we broke down in how to dictate quotation marks and special characters.
The fix is the same as always: type the two characters, then talk. Reaching over to hit - and space costs you well under a second, and it works every time. Voice is worth using where it is fast, and typing is worth using where it is certain. Lists are one of the clearest places where mixing the two beats insisting on either.
App by app: what actually happens
Apple Notes
The most forgiving of the bunch. Start a bulleted list from the formatting menu or with the dash-space shortcut, and "new line" continues the list cleanly. Two Returns exit. Checklists behave the same way, which makes Notes an excellent target for dictating a task list while your hands are busy.
Microsoft Word and Pages
Both continue lists on Return exactly as expected. The wrinkle is autoformat: Word in particular sometimes converts things you did not ask it to convert, including turning a dictated hyphen at the start of a line into a bullet unexpectedly. That is usually helpful, but if a list appears out of nowhere mid-paragraph, autoformat is the culprit, not dictation.
Google Docs and other browser editors
Lists continue normally. The thing to watch in the browser is that some editors intercept keystrokes in ways that make line breaks land oddly in comments and suggestion boxes as opposed to the main document body. If a list works in the document but not in a comment, that is the editor's comment field being a simpler text box, not a dictation failure.
Notion, Obsidian, and outliners
These are the best case. They are built around block structure, so every Return is a new block and the dash-space shortcut is native. Dictating a long flat list into an outliner and then restructuring with Tab is arguably the single most efficient voice workflow there is, because the tool is designed for exactly that shape of editing.
Slack, Messages, and chat apps
Stop before you try. In most chat apps, Return sends the message. Saying "new line" in a Slack composer will fire off item one as a standalone message, then item two, and so on, until your teammate has a notification stack of six fragments.
Two options. Either use the app's soft-break shortcut, which is usually Shift-Return, before continuing, or dictate the whole list somewhere else and paste it in. For anything more than three items, drafting it in a notes app first is faster and far less embarrassing.
Compose windows in mail clients are rich text editors, so lists behave normally. The one habit worth building is creating the list before you start talking, because reaching for the formatting toolbar mid-sentence is the moment most people lose the thread of what they were going to say.
How to talk a list out loud
The mechanics above get the bullets on the page. Getting a list that is actually good to read is a different skill, and it is mostly about how you phrase things while speaking.
One idea per item
Spoken lists tend to sprawl, because talking is cheap and there is no physical cost to adding another clause. When you catch yourself saying "and also" inside an item, that is your signal to say "new line" instead. The rule is one idea per bullet. If it needs an "and also," it is two bullets.
Keep items parallel
Good lists start each item the same grammatical way: all verbs, or all nouns, or all questions. Spoken lists drift out of parallel almost immediately because your brain reaches for whatever phrasing comes next. Decide the shape before you start. If item one begins with a verb, say every item beginning with a verb. It costs nothing at dictation time and saves a full editing pass later.
Do not narrate the structure
Resist saying "first," "second," "next," and "finally" inside items. The list already conveys sequence visually. Narrating it produces bullets that read as a transcript of someone talking about a list rather than as a list.
Overshoot, then cut
The genuine advantage of dictating lists is volume. You can produce fifteen candidate items in the time typing would give you five. Take that trade. Dump everything, including the weak items, then delete the bottom third. Editing down from too much is a faster path to a good list than trying to produce only good items in the first place.
Troubleshooting
It typed the words "new line" instead of breaking the line
Three usual causes. First, you ran the command into the surrounding words without a beat of silence, so it was heard as part of the sentence. Pause briefly before and after. Second, your dictation language variant does not match how you speak, which degrades command recognition specifically because commands are short and have no surrounding context to disambiguate them. Third, background noise clipped the command. Short phrases are the first thing noise destroys.
The list broke after the first item
You said "new paragraph," or the app treats a double break as an exit. Switch to "new line." If the app still exits, it is one of those editors that ends lists on any hard break, in which case press Return manually and continue dictating the next item.
Every bullet came out as one giant paragraph
The line break command never fired at all. Check whether you actually created a list first. If the cursor is in a plain paragraph rather than a list item, breaks produce more paragraphs, not more bullets, and nothing about how you speak will change that.
The bullets are there but the text is a mess
That is a different problem. Long dictated items with no internal punctuation are hard to read no matter how well the list is structured. Say your commas. If cleaning up after the fact is the bottleneck, the ways to correct dictation mistakes covers the repair techniques that are quicker than retyping.
The same wrong word keeps appearing in every list
If you write the same kinds of lists repeatedly, you have a fixed vocabulary: project names, client names, product SKUs, internal acronyms. When those come out wrong, no amount of speaking more clearly will fix them, because the error is in what the engine considers a plausible word, not in your pronunciation. That is a dictionary problem, and it needs a dictionary fix.
Where Voice Keyboard Pro fits
Everything above applies to any dictation system. A few things do get meaningfully easier with a hold-to-talk tool, and lists are the clearest example.
Voice Keyboard Pro on Mac lives in the menu bar. You hold a hotkey, speak, release, and the text appears at your cursor in whatever app is in front of you. For lists, that push-to-talk model maps naturally onto the structure: one press per item. Hold, say the item, release. The release itself becomes your item boundary, which means you can think between bullets without a timeout ending your session or a silence gap getting interpreted as punctuation. You press Return, hold again, and say the next one.
Because the text is inserted at the cursor system-wide, there is nothing to install into Word, nothing to enable in Notion, no browser extension for Google Docs. If you can click into the field, you can talk into it, which is why the same workflow carries across every app in the list above.
Smart Vocabulary handles the recurring-vocabulary problem directly. It is a personal dictionary with replacement rules, so the client name that keeps coming out as a similar-sounding common word gets fixed at the source, in every list you ever dictate, rather than corrected by hand each time. If you build the same weekly status list with the same six project code names in it, this is the difference between voice being a nice idea and voice being faster than typing.
On iPhone, Voice Keyboard Pro is a keyboard with a built-in mic button, so it works inside any app, including the notes and task apps where lists actually get made. Voice Edit is the piece that matters most for list work on a phone: instead of hunting for a cursor position between two bullets with your fingertip, you speak the change you want and it gets applied. Anyone who has tried to fix the third item of a seven-item list on a phone screen knows exactly how much that is worth.
On privacy, our server stores only operational pings. No audio, no transcript content. Your lists are your lists.
There is a free tier with daily limits if you want to test the workflow on a real document before deciding. Pro is $4.99 a month or $34.99 a year.
Frequently asked questions
Is there any spoken command that creates a bullet?
Not on Mac or iPhone built-in dictation. Some dedicated dictation packages in specialised fields implement formatting commands, but standard system dictation does not, and words like "bullet point" or "new bullet" will be typed as text. The editor-owns-the-list approach in this guide is the reliable path.
What about voice control, as opposed to dictation?
Voice Control on Mac and iPhone is a separate accessibility feature that does understand interface commands, and it can press keys for you. It is a genuinely different tool with a different mode of operation, and it comes with its own trade-offs around commands firing when you did not intend them. It is worth exploring if hands-free operation is a requirement rather than a preference, but it is not what most people mean when they say dictation.
Can I dictate a list into a plain text field with no formatting?
Yes, and it is often simpler. Type a dash and a space, dictate the item, say "new line," type a dash and a space again. There are no automatic markers in plain text, so you supply them. For a long list, dictate the lines first and add the dashes afterward with a few keystrokes.
Why does my list work in one app but not another?
Because list behaviour belongs to the app, not to dictation. Different editors handle Return, double Return, and soft breaks differently. If a technique works in Notes but not in a web form, the web form is a simpler text box that does not implement lists at all.
What is the fastest overall way to produce a long list by voice?
Open a plain notes app or an outliner. Start the list once. Talk every item without stopping, including the bad ones. Then restructure with Tab, delete the weak items, and paste the result wherever it needed to go. The generation pass and the arranging pass are separate jobs, and keeping them separate is what makes voice fast rather than merely novel.