How to dictate in a second language (and when you shouldn't)

There are two ways to dictate in a second language: speak it directly and let the engine transcribe you, or dictate in the language you think in and translate the result in one click. The first works if you are conversationally fluent; the second is usually faster and more precise, because hesitation — the thing that ruins dictation — mostly disappears in your native language. Here is an honest look at both workflows, where each one breaks, and what the tools actually support.

Writing in a second language is a double tax

When you write in a second language, you are doing two jobs at once: deciding what to say, and translating it while you say it. Every sentence gets slower — you second-guess spelling, reach for a word that will not come, then settle for a simpler one. The message that leaves your keyboard is rarely the message you had in your head; it is the version of it you could afford.

Dictation looks like the obvious fix, since speaking is around four times faster than typing. But dictating in the second language often just moves the tax: now the word-hunting and the hesitations happen out loud, and the engine transcribes all of it.

Workflow 1: dictate directly in the second language

If you are conversationally fluent, this works — and it is good practice. Modern cloud speech engines cover 100+ languages and handle accented speech far better than the built-in dictation of a few years ago, so a French accent in English or a German accent in Spanish is no longer the obstacle it used to be. Three things make it go well:

• Set the language deliberately. Apple's built-in dictation transcribes one language at a time, switched from the keyboard; dedicated tools like Wispr Flow auto-detect what you speak.
• Speak in full sentences. Engines lean on context to choose between similar-sounding words; fragments give them nothing to lean on.
• Never spell words out. Say them normally and fix spelling in the proofread — spelling aloud confuses engines more than it helps them.

Where this workflow breaks is hesitation. A speech engine transcribes what you actually said — including the pause, the restart, and the word you settled for because the right one would not come. An AI cleanup pass can strip the false starts, but it cannot restore nuance you never managed to express. In a second language, that happens every few sentences, which is why so many people try dictating in one once and quietly go back to typing.

Workflow 2: think in your language, send in theirs

This is the workflow that changes things for non-native speakers. Dictate in the language you think in, at full speed, rambling allowed. Let the AI formatting pass turn it into clean, correctly punctuated text — in the tone you picked, formal for the client, casual for the team chat. Then translate the result in one click, skim it, send it.

Why it wins: nuance survives. You expressed the idea natively, with the precision and register you actually command, and the translation carries that over — instead of flattening your message to the vocabulary you can retrieve under pressure. It is also simply faster: no mid-sentence word hunts, no restarts, no accent tax.

The honest caveat: you should read the target language well enough to sanity-check the result before sending. For most people that is exactly the situation — reading a language is much easier than writing it — and it is what makes this workflow work.

What the tools actually support

One more honest note: everything in this table that translates or reformats your speech runs in the cloud — Swifly included. If your work requires fully offline processing, dictate with a local tool and translate separately.

Three checks before you hit send

• Proper nouns. Names of people, products and places are where every speech engine still slips — and they should come through translation untouched. Check both.
• Dates and numbers. "11/03" is March 11 in one country and November 3 in another. After translating, make sure dates read unambiguously for the recipient — no engine can know which convention you meant.
• The formal "you". If the target language distinguishes formal and informal address — tu/vous, du/Sie, tú/usted — check which one the translation chose. Getting it wrong is the fastest way to sound off to a native reader.

The takeaway

Dictating in a second language is not one skill but two workflows, and choosing the right one matters more than any setting. Fluent and confident? Dictate directly, in full sentences, and proofread the names. Anything less? Dictate in the language you think in and translate in one click — you will be faster, and you will sound more like yourself in both languages.