Short answer: Dictate an address in one continuous pass, saying it the way you would read it aloud, then verify every digit by eye before sending. Say street numbers as separate digits, name each punctuation mark, and save frequently used addresses as Smart Vocabulary entries you trigger with a short phrase.
Addresses are the hardest short thing to dictate. A paragraph of prose is forgiving: if one word comes out slightly off, the sentence around it still makes sense and your eye catches the error immediately. An address has no redundancy at all. Every character carries meaning, nothing provides context for anything else, and a single wrong digit produces something that looks entirely correct and is completely wrong.
That combination is why people who dictate everything else still type addresses by hand. It is a reasonable instinct, and it is also more caution than the task requires. Most address dictation errors come from a small, predictable set of causes, and once you know what they are, you can speak an address as fast as you can read one and check it in three seconds.
This guide covers what actually breaks, how to say each component, how to handle non-US formats, and how to stop re-dictating the same six addresses every week.
Why Addresses Break Dictation
Five distinct problems hide inside what looks like one problem.
Digits have no context. Transcription works by using surrounding words to resolve ambiguity. In "the meeting starts at fifteen hundred," the surrounding words tell the engine what kind of number it is dealing with. In "1517," there is nothing. The engine has to decide between 1517, 15 17, and fifteen hundred seventeen with no help at all.
Street names are ordinary words used unusually. A street called Wright, Reed, Vale, or Poole is a homophone of a common word. In prose, context resolves it. In an address, "1200 Reed Street" and "1200 Read Street" are equally plausible strings, and only one of them exists.
Abbreviations are a formatting decision, not a speech act. Nobody says "Saint" and "Street" differently enough for a machine to always separate them, and nobody speaks the letters S-T. Whether you get "Street," "St," or "St." depends on conventions you cannot control by pronunciation alone.
Unit designators collide with the number that follows. "Apartment 4B" contains a word, a digit, and a letter in a row. "Suite 200" versus "Sweet 200" is a real failure mode. So is "Unit 12" turning into "Unit twelve."
Two-letter state codes are not words. Saying "CA" produces different results than saying "California," and saying "OR" for Oregon is nearly guaranteed to produce the conjunction instead. Postal codes have the same character: they are strings of symbols, not language.
Notice that all five are structural, not accuracy problems. The transcription engine is not mishearing you. It is making reasonable formatting decisions about content that carries no linguistic signal about how it should be formatted.
The One Rule That Prevents Most Errors
Speak the words, verify the digits.
Dictate the whole address in one pass at a normal pace. Then read the numbers back off the screen before you send, save, or print. Not the whole address, just the numeric parts: the street number, the unit, the postal code.
The reason to split it this way is that prose defends itself and data does not. If a street name comes out wrong, it usually looks wrong. If a digit comes out wrong, it looks exactly as correct as the right digit, and it will keep looking correct through every downstream system that touches it. The parcel goes to the wrong building. The invoice goes to the wrong office. Nobody notices until it matters.
A misspelled word gets caught by the next person who reads it. A wrong house number gets caught by a delivery driver three days later.
This is the same principle we apply to dictating email addresses and URLs, and to dictating numbers and dates. Speak the human-readable part, then look at the machine-readable part with your eyes.
How to Say Each Component
The street number
Say it the way you would read it to a person over the phone, digit by digit, at a steady pace. For 1517, say "one five one seven." For 42, "four two" or "forty two" both work reliably because short numbers are unambiguous.
The failure case to avoid is the natural spoken shorthand. "Fifteen seventeen" is how most people say a four-digit street number out loud, and it is genuinely ambiguous: it could be 1517 or 15 17. Digit-by-digit removes the guess.
For hyphenated or split house numbers, say the hyphen explicitly: "one four dash two two" for 14-22. For numbers with a fractional part, which appear in some older US cities, say "one two three and a half" and expect to fix the formatting by hand.
Directionals
Say the full word: "North Clark Street," not "N Clark Street." Speaking the single letter N produces unpredictable results, and the full word is what most address formats expect anyway. If your system requires the abbreviated form, dictate the full word and let a replacement rule shorten it, which we cover below.
Watch the directional-that-is-also-a-name case. "West Street" and "South Boulevard" are real street names in many cities, and the directional slot and the name slot both contain a compass word. Dictate it and then confirm the result matches the source you copied it from.
Street suffixes
Say the full word: Street, Avenue, Boulevard, Drive, Lane, Court, Place, Terrace, Parkway, Highway. Do not attempt to speak the abbreviation. "Ave" spoken aloud is more likely to produce "have" or "a v" than "Ave."
If you need abbreviated output for a shipping label or a database field, dictate the full word and abbreviate afterward, or set up a replacement rule. Getting the correct full word and shortening it is far more reliable than getting an abbreviation directly.
Unit, apartment, and suite
Say the designator, pause very briefly, then the identifier digit by digit and letter by letter. "Apartment, four b." "Suite, two zero zero." The tiny pause is doing real work: it separates the word from the alphanumeric string so they are not resolved as one token.
Single letters after a number are the most error-prone element in any address. B, D, E, G, P, T, V, and Z all share a vowel sound and get confused with one another constantly. This is the one place where slowing down materially changes the outcome. Give each letter its own beat, and check letters visually every single time.
City and state
Say the city name normally. For the state, say the full name: "California," not "CA." Full state names transcribe reliably because they are ordinary proper nouns. Two-letter codes are not words and behave badly, and Oregon in particular will hand you the word "or" more often than not.
If you need two-letter codes in the output, this is exactly what replacement rules are for. Dictate "California," get CA.
ZIP and postal codes
Digit by digit, always. "Nine four one zero seven." Never "ninety four one oh seven," which invites the engine to write out words or to group the digits wrongly.
For ZIP+4, say the dash: "nine four one zero seven dash one two three four." For codes that begin with a zero, dictate them and then check the leading zero survived, because leading zeros are the single most commonly dropped character in any numeric string. Anyone dictating addresses in New England or New Jersey should build this check into the habit permanently.
Punctuation and line breaks
Say the punctuation you want. "Comma" gives you a comma. For a genuine line break between the street line and the city line, say "new line." Dictation does not infer address formatting from content, so if you do not name the break, you get one continuous line.
Many shipping and CRM forms have separate fields for each line anyway, which sidesteps this entirely. Click into the field, dictate that field's content, tab to the next.
Non-US Address Formats
The general rule holds everywhere: words spoken normally, alphanumeric strings spoken character by character, then verified visually. The specifics differ.
UK postcodes are alphanumeric in both halves and are the hardest common case in any language. Say each character with a clear beat and a small pause between the outward and inward halves. Letters that sound alike, particularly M and N, are the usual culprits. Check these letter by letter every time, without exception.
Canadian postal codes alternate letters and digits, which actually helps: the alternation makes the pattern predictable, so an error usually breaks the pattern visibly. Say each character separately and confirm the alternation is intact.
Indian PIN codes are six digits with no letters, so they behave like US ZIP codes. Say them digit by digit and watch for grouping, since six-digit strings are prone to being split into pairs.
European formats commonly put the postal code before the city and the house number after the street name. Dictate in the order the form expects rather than the order you are used to, or you will spend more time reordering than you saved.
Two-way translation in Voice Keyboard Pro covers 24 languages, which helps when you are writing the surrounding message in another language. Addresses themselves should not be translated. A street name is a proper noun and belongs in its local form, since the delivery driver at the destination reads the local form.
Stop Re-dictating the Same Addresses
Most people who dictate addresses regularly are dictating a small set repeatedly: the office, the warehouse, the registered business address, two or three regular clients, home. Speaking those out character by character every week is wasted effort.
Smart Vocabulary is a personal dictionary with replacement rules, and this is one of its best uses. Set up a short trigger phrase that expands to a full stored address. Say "office address" and get the complete, correctly formatted block. Say "warehouse address" and get the other one.
This is not just faster. It is more accurate, because the stored version was typed once, checked once, and is now correct forever. Errors cannot creep back in. For any address you send more than twice a month, storing it is straightforwardly better than dictating it.
The same mechanism handles formatting conversions. Rules that turn spoken full words into the abbreviated forms your systems expect, like Street to St or California to CA, let you speak naturally and still produce the format your database wants. Our guide on building a custom vocabulary covers setting these up.
Local street names are worth adding too. Every region has streets whose names are unusual spellings, family names, or words from another language. If you work in one area, twenty entries covering the streets you write most will remove nearly all of your remaining street-name errors.
On Mac
Voice Keyboard Pro is a menu bar app. Hold your hotkey, speak, release, and the text appears at your cursor in whatever app is in front of you. Nothing is installed into your CRM, your shipping software, or your browser, so it works identically in a web form, a native app, and a spreadsheet cell.
Three practical notes for address work:
- Click into the field first. Address forms are dense with fields, and text lands where the cursor actually is, not where you were looking. This is the most common cause of "it did not work" reports on form-heavy pages.
- One field, one dictation. Rather than dictating an entire address into one field and rearranging it, dictate field by field and tab between them. It feels slower and is faster, because you skip the cleanup.
- Watch for autocomplete. Many address forms have their own lookup that fires as text arrives and can replace what you dictated with a suggestion. Look at the final field content, not at what you said.
On iPhone
On iPhone, Voice Keyboard Pro is a keyboard with a microphone button, so it works in any app: a shipping app, a delivery note, Messages, a form in Safari. Tap the microphone, speak the address, and it appears where you were typing.
The phone case where this earns its keep is the address you are given verbally. Someone tells you where to send something while you are standing in a hallway. Speaking it back as you hear it is dramatically faster and more accurate than thumb-typing a postal code on glass.
Voice Edit is useful here too. If one component is wrong, you can speak the correction rather than placing a cursor between two characters in a small field, which is the fiddliest interaction on a phone and the one most likely to cause a second error while fixing the first.
Where This Matters Most
Shipping and fulfillment. High volume, tight deadlines, and a wrong digit costs a real parcel. Store your regular destinations, dictate the one-off ones field by field, verify numerics before printing the label.
CRM and sales records. Addresses entered into a CRM get reused for years by people who were not there when they were typed. Errors compound. The verify-the-digits habit pays off over a long horizon here more than anywhere else.
Real estate. Property addresses appear in listings, contracts, and marketing copy, often several times per property. Storing the current listing's address as a vocabulary entry for the duration of the listing is a small trick that removes a whole class of embarrassing errors. We cover the broader workflow in dictating real estate listings.
Invoicing and admin. Billing addresses are the definition of low-redundancy data. Wrong ones create payment delays that take weeks to unwind, which is a poor return on the fifteen seconds saved by not checking.
Troubleshooting
Numbers come out as words. Long spoken number phrases are more likely to be written out in full. Digit by digit reduces this substantially. For a stubborn field, type the number and dictate the rest.
The leading zero disappears. Check it. This is the most predictable dictation error involving numeric strings, and no amount of careful speaking fully prevents it. Build the check into the habit rather than trying to prevent the error.
Unit letters keep coming out wrong. Slow down and give each letter its own beat. If a specific letter fails repeatedly, a replacement rule can force it. Consider whether a headset microphone would help, since single-letter accuracy is more sensitive to microphone quality than sentence accuracy is.
Everything lands on one line. Say "new line" where you want a break, or use the form's separate fields.
The form overwrites what you dictated. That is the form's own address autocomplete, not the dictation. Dictate, then look at what the field settled on before moving to the next.
Frequently Asked Questions
Should I just type addresses instead?
For a single address, typing and dictating come out roughly even once verification is included. Dictation wins clearly in three situations: when you are reading an address aloud from a source and would otherwise be looking back and forth, when you are on a phone where typing is slow, and when the address is stored as a vocabulary entry and expands from a two-word trigger. It wins less clearly on a one-off desktop entry, and that is a fine place to keep typing.
Can I dictate an address into a Word or Excel template?
Yes. Text goes wherever your cursor is, including a spreadsheet cell or a mail-merge field. For spreadsheets, dictate into the formula bar or the cell and press Return yourself, since spoken "new line" behaves differently inside a cell than in a document.
Does it handle international characters in street names?
Accented characters in Latin-script languages generally come through correctly when you dictate in that language. Mixing languages within a single dictation is where it gets unreliable, so dictate a foreign-language address as its own separate pass rather than embedded mid-sentence in English.
Is my address data sent anywhere?
Audio is transcribed and not stored, and our servers keep operational pings only, meaning counts and timings rather than content. No transcript text is retained on the server. If you handle addresses under a specific regulatory obligation, review our privacy policy against your own requirements rather than taking a summary as sufficient.
What does it cost?
There is a free tier with daily limits. Pro is $4.99 a month or $34.99 a year, covering the Mac app and the iPhone keyboard together.
The Short Version
Say the words normally. Say the digits one at a time. Say the punctuation you want. Then look at the numbers with your eyes before you commit, because a wrong digit will never announce itself. Store the addresses you use repeatedly so they stop being a dictation problem at all.
That is the entire method, and it takes about a day to become automatic. Voice Keyboard Pro has a free tier on Mac and iPhone. Try it on the next address someone reads out to you, and check the digits.