Mac Dictation Not Working in Threads? 10 Fixes That Work

Short answer: If Mac dictation is not working in Threads, click inside the post or reply box until a cursor blinks, then dictate. On a Mac, Threads is a website with no voice typing of its own, so words go wherever focus is, and one post holds only 500 characters.

You have a reply worth more than a one-liner, a take you want to get out while the conversation is still going, or a thread you have been meaning to write all week, and saying it would be far quicker than typing it. You press your dictation shortcut on your Mac, speak, and nothing appears. Or your sentence turns up in the search box. Or the words arrive, the Post button stops responding, and the end of what you said is marked as too long.

Four facts about Threads on a Mac explain almost all of it. First, on a Mac Threads is a website with no voice typing of its own, so dictation comes from macOS or from a dictation app, and both deliver text to whatever has keyboard focus, exactly as if you had typed it. Second, a Threads page holds many separate text boxes, and the feed between them is not one of them. Third, a single post holds 500 characters, and people speak far faster than they type, so a dictated thought outgrows a post in well under a minute. Fourth, a post that has gone out can be changed only briefly, so the read-through has to happen before you click Post.

So most Threads dictation problems on a Mac come down to where focus was, how much you said, and what happened after you said it. They are rarely about your microphone. This guide works through every cause in order, starting with the most common one. If dictation is failing in every app on your Mac and not only in Threads, start with our complete guide to Mac dictation not working instead. Threads changes its website often, so exact button names and positions may differ slightly from what you see.

First, which Threads are you in?

On a Mac, "Threads" can mean several different places, and a fix that works in one may not apply in another.

• The site in a browser tab. The feed, profiles, search and your activity at threads.com. This is where the composer and the reply boxes live.
• An installed web app. Safari and Chrome can install the site as a window of its own with an icon in the Dock. It looks like a Mac app, but it is the same website, and macOS treats it as a separate app from your browser.
• Columns. The website can show several feeds side by side, such as For you, Following, a saved search or your activity. Each column scrolls on its own, but the page still has only one cursor.
• The composer window. The window that opens when you start a new post or a reply, with the post box, room to add more posts to a thread, and a few smaller controls underneath.
• Messages. Threads has been adding private messages. If your account has them, each conversation has its own message box, and it follows chat rules rather than post rules.
• A second profile. Many people sign in to Threads through Instagram, and some run more than one profile. A post goes out from whichever profile is signed in to that tab.

At the time of writing, most people use Threads on a Mac through a browser, so each of these is a web page. Each browser, browser profile and installed web app also keeps its own sign-in, so the profile you are signed in to in Safari may not be the one in your Dock app. Knowing which page and which profile you are in settles a good share of the confusion below.

How dictation reaches Threads on a Mac

Apple dictation is built into macOS. You start it with the dictation shortcut, usually the microphone key or whichever shortcut is set in System Settings under Keyboard, or from Edit, then Start Dictation in your browser's menu bar. It sends its text to whichever field has keyboard focus. Threads does not need microphone permission for that, because it is your Mac that is listening, not the web page.

Menu bar dictation apps, including ours, look much the same from Threads' side. They put text at your cursor, often the way a paste does. They need their own Microphone permission, plus Accessibility permission to put text into other apps, under System Settings, then Privacy & Security. Neither Threads nor your browser needs anything extra, and there is no extension to install.

If your browser ever asks whether Threads can use the microphone, that request is for the site's own media features. It has nothing to do with dictation, and allowing or blocking it will not change whether dictated text appears.

That leaves one rule to remember: dictated text goes to whatever has focus, and Threads treats it exactly like typing. A sentence in the composer is a post. The same sentence in the search field is a search, and with nothing in focus at all it goes nowhere useful.

The 30-second TextEdit test

Before you change anything, open TextEdit, create a blank document, start dictation and say a sentence. Then go back to Threads, open the composer, click in the post box so the cursor blinks there, and dictate the same sentence. Do not click Post. Select the text and delete it when you are done.

• If nothing appears in TextEdit either, the problem is dictation on your Mac, not Threads. Go to fix 10.
• If TextEdit works but nothing appears in Threads, go to fixes 1 and 9.
• If your words appeared in search, a different reply or the wrong post in a thread, go to fix 2.
• If the words arrived but Post will not work, go to fix 3.
• If a message went before you finished, or a mention appeared that you never chose, go to fixes 4 and 5.
• If words you never said turned up in your text, go to fix 6.
• If your words were there and are gone now, go to fix 7.

Command-Z usually works in Threads' text boxes. If a paragraph lands somewhere it should not, undo it before you try to repair it by hand.

The 10 fixes, in order

1. Click in the post box until the cursor blinks

Threads gives you more than one way to start writing. The line at the top of the feed that invites you to start a post opens the composer when you click it. The create button in the sidebar does the same. The reply icon under a post opens a composer for a reply, with the original post shown above it. In each case the composer is ready for text only once the cursor is blinking inside it.

The feed is not a text field. If you start dictating while you are still scrolling and reading, there is nowhere for the words to go. With some dictation tools nothing happens at all. With tools that send text as a series of key presses, the browser may act on some of them instead. The Space bar, for example, scrolls a page when no field has focus, so the feed jumps and the sentence disappears.

What to do:

• Open the composer, click in the post box, look for the blinking cursor, and only then start dictation.
• If you have since clicked on an image you attached, one of the options under the text, or the page behind the window, click back into the text before you speak.
• If the cursor is blinking in the right box and dictated text still does not arrive, go to fixes 9 and 10.

2. Check which box has the cursor

A Threads page can hold a surprising number of text fields: the search field, the composer, the reply box under a post you have opened, each post in a thread you are building, a message conversation, and in the column view, a search column of its own. Only one of them has the cursor, and scrolling does not move it. If you clicked into a box, scrolled away and then spoke, the words go into the box you left behind, which may now be out of sight.

• Reply, quote or new post. A reply sits under the original in the conversation. A quote puts the original inside a new post of your own. A new post has no link to either. The composers look alike, so check what is shown above the box before you speak.
• Posts in a thread. When you add a second or third post to a thread, each one is its own box. Your words go into whichever has the cursor, which may not be the last one.
• Search. A paragraph dictated into the search field becomes a search, and if a Return follows, a page of results replaces what you were reading. Press Command-A inside the field and delete. The browser's Back button returns you to the page you left.
• The small fields. Your bio, your link, and the description you can add to an image are all separate fields, each with a limit of its own.

The habit that prevents all of these is to click in the box you mean immediately before you speak. If words land in the wrong box, select them, cut them with Command-X, click where they belong and paste with Command-V.

3. Stay inside the 500-character limit

A single Threads post holds up to 500 characters. In ordinary English that is roughly 80 to 100 words. People speak at around 130 to 150 words per minute, so you reach the limit after about 35 to 45 seconds of talking. Typing rarely overshoots by much, because you watch the text grow as you go. Dictation overshoots whenever you have more than a couple of points to make.

Once a post runs past the limit, Threads will not publish it until you cut it back. The words are all still there. Nothing is wrong with dictation. You simply said more than one post holds.

What to do:

• Dictate first, cut second. It is easier to trim a complete thought than to speak in 500-character pieces. Say the whole thing, then remove what the post can live without.
• Turn it into a thread. Add another post below the first in the composer, cut the overflow and paste it there. Each post in the thread has its own limit.
• Draft long pieces elsewhere. Dictate the whole thread in TextEdit or Notes, break it into posts at natural points, and paste them in one at a time.

4. Know what Return does in each box

The Return key does different jobs in different parts of Threads.

• In the composer, Return starts a new line. A post is not published until you click Post.
• In the search field, Return runs the search, and the results replace whatever you were looking at.
• In a message box, if your account has messages, Return usually sends, as it does in most chat apps. Shift-Return gives a new line without sending.
• With a suggestion list open, Return picks the highlighted item from the list instead of doing anything else. See fix 5.

This matters because of how a spoken line break is delivered. If you say "new line" or "new paragraph" and your dictation tool passes that to the page as a press of the Return key, a message is sent at that point, or a search runs, or a suggestion is chosen. Many web composers also treat a Return-based key combination as a shortcut for posting, so keep your hands away from the Return key while a draft is still unread.

What to do:

• Dictate messages as one paragraph, without spoken line breaks, and add breaks by hand afterwards.
• For a carefully laid-out post, dictate it in TextEdit or Notes first and paste it in. Pasted line breaks are usually kept.

5. Dictate the words, then add mentions and the tag by hand

The composer watches what arrives and reacts to it. An @ sign opens a list of profiles to mention. A # sign opens a picker for a topic tag. Threads is built around a single topic tag on a post rather than a string of hashtags, and the picker exists to help you choose it.

Dictated text lands as characters, so all of that still happens. While a list is open, the Return and Tab keys choose from it, so a dictated sentence containing an @ sign can open the list, and the next key press can select a profile you never meant to mention. That person is notified. Dictation also struggles with this kind of text in the first place. A handle is rarely a dictionary word, and a tag is often several words run together, so dictation hears both as ordinary words, spaced out and in lower case.

What to do:

• Say the sentence first, stop dictation, then type the @ yourself and choose the profile from the list by clicking it.
• Add the topic tag the same way, by typing # and picking from the list.
• Before you post, look at the highlighted text. Mentions, tags and links stand out from the rest of the post, so an unintended one is easy to spot.
• Paste links after the text. A dictated web address needs correcting anyway.

6. Pause videos before you speak

The Threads feed carries video, and some of it plays as you scroll past. If a clip is playing with sound through your Mac's speakers, the microphone hears it along with you. Dictation then does one of two things: it transcribes the other voice into your post, or the background sound makes it misjudge where your sentences start and stop. A video or podcast playing in another tab has the same effect.

What to do:

• Pause any video you can see, or mute it, before you start dictating.
• Check other tabs for sound. Safari and Chrome show a speaker icon on a tab that is playing audio.
• Use headphones if you like to dictate while something plays, so the speakers are not feeding the microphone.

7. Keep an unposted draft safe

Text you have not posted yet exists only in the page in front of you. Reload the tab, follow a notification, press Escape or click outside the composer window, and the composer can close or ask whether to discard what you wrote. Threads may offer to save it as a draft. That is worth accepting, but do not count on a draft saved on the website waiting for you in the phone app later. A browser that restarts for an update can take an unsaved post with it, too.

• For anything longer than a single post, dictate in TextEdit or Notes and paste the result into Threads.
• If you dictate in place, press Command-A then Command-C in the box before you click anything else, so a copy sits on the clipboard.
• When you need to look something up mid-post, open it in a new tab so the tab with your draft stays as it is.

8. Read it before you post

Dictation mistakes survive a quick glance better than typing mistakes do. A typing slip looks wrong on the page. A dictation slip is a correctly spelled wrong word: a name heard as a similar name, "can" where you said "can't", a number one digit short. Read the whole post once, slowly, as if someone else had written it.

At the time of writing, Threads lets you edit a post for only a short time after it goes out. After that, the only correction is to delete it and post again, and anyone who already saw, quoted or replied to the first version saw the mistake. While you are reading, check three more things:

• The profile. The picture and name beside the composer show which profile the post will come from. If you run a work profile as well as a personal one, look every time.
• The kind of post. A reply shows the post it answers above the box. If you meant to start a post of your own, you are in the wrong composer.
• Who can reply. The composer shows who will be able to reply to and quote the post. Change it before you post if it is not what you want.

9. Sign back in when Threads asks, and clear Secure Input

A session can expire while a tab sits in the background, and Threads may ask you to sign in again, often through your Instagram account. If a sign-in screen is in front of you while your eyes are on your notes, a dictated paragraph goes nowhere, because the page is waiting for a password or a code.

There is a second effect for dictation apps. While a password field is active, macOS turns on Secure Input, which stops other apps from reading or sending keystrokes. A dictation app may not see its hotkey, or may not be able to deliver its text, for as long as the cursor sits in that password box. A password manager prompt can do the same. Sign in, let the page load again, click back into the box you were using and try once more. If your hotkey stopped working in every app right after you typed a password somewhere, look for a password field still waiting in another window and close it.

10. Rule out the browser, then check dictation on your Mac

Threads runs in a browser, so the browser is part of the problem space. Open Threads in a private window or a different browser, sign in, and dictate there. If it works, something in your everyday browser profile is interfering.

Extensions are the usual suspects. Ad blockers and privacy tools change how pages load and behave. Writing assistants and grammar checkers attach themselves to editable text, and they can move the cursor or rewrite text as it arrives. Turn extensions off one at a time until dictation behaves.

If you use a dictation app, check its two permissions under System Settings, then Privacy & Security: Microphone, so it can hear you, and Accessibility, so it can put text into your browser. After you grant a permission, quit the app and open it again. If your dictation shortcut matches a browser shortcut, the browser may act on it first, so try a different key.

If dictation failed in TextEdit too, Threads is not the problem. Open System Settings, go to Keyboard, and make sure Dictation is on. Check which shortcut it uses and that the dictation language matches the language you are speaking. Check the microphone as well: a video call or a screen recorder can keep hold of it, and an unplugged headset can leave your Mac listening to the wrong input. Then restart your Mac, which clears a stuck dictation service in one step.

Threads quirks that look like broken dictation

• Post will not work. Either the post is over 500 characters, as in fix 3, or the box is empty because your words went somewhere else, as in fix 2.
• There is no way to reply. The author may have limited who can reply to that post. No dictation setting changes that.
• Your reply posted, but others say they cannot see it. Authors can hide replies on their own posts, and if your profile is private, only your followers see what you post. Dictation did its job. The audience is the issue.
• The feed moved under you. New posts load and the page shifts. Your cursor may still be in a reply box that has scrolled out of view.
• Somebody else's words are in your post. A video was playing within earshot of the microphone. See fix 6.
• The post came from the wrong profile. The words are right and the name above them is wrong. See fix 8.

Quick triage

• Nothing appears anywhere on Threads: no box had the cursor, or a sign-in screen is waiting. Fixes 1 and 9.
• The words went somewhere else: another box had the cursor. Fix 2.
• Post will not work: the post is over 500 characters. Fix 3.
• A message went early, or a search ran: a line break arrived as Return. Fix 4.
• Someone was mentioned by mistake: a suggestion list took a key press. Fix 5.
• Odd words in the post: a video was playing. Fix 6.
• The text vanished: the composer closed or the page reloaded. Fix 7.
• A mistake went public: edit it quickly, or delete and post again. Fix 8.
• Nothing works in any app: it is your Mac, not Threads. Fix 10.

Threads on a Mac versus on iPhone

The two behave differently enough that advice for one rarely transfers to the other. On a Mac, Threads is a web page, dictation starts from a shortcut or a hotkey, and nearly every problem comes down to focus, the character count and the browser. On an iPhone, Threads is an app, dictation lives on the keyboard, and the usual causes are a missing mic key, a setting that has been switched off, or an audio accessory that has taken over the microphone.

If your phone is where the trouble is, our guide to iPhone dictation not working in Threads covers that side step by step.

A dictation workflow that suits Threads

Most adults type at around 40 words per minute and speak at 130 to 150. On Threads the gain is not in a one-line reply, which is quick either way. It is in replies that need a real paragraph, in threads with several posts, and in image descriptions, which many people skip because typing them feels like a chore. A few habits keep it smooth.

• Single posts. Open the composer, check for the cursor, say the thought in full, then trim it to fit. Read it once and click Post.
• Threads with several posts. Dictate the whole piece in a document, break it into posts at natural points, and paste each into its own box. Read the thread in order before you publish it.
• Replies. Open the reply composer, click in it, speak one paragraph, and read it before you post.
• Image descriptions. If the composer offers a description for an image you have attached, click into that field and say what the picture shows. A sentence or two of plain description is what the field is for.

For the full how-to, including punctuation commands and keeping a casual tone, see our guide on how to dictate on Threads.

One hotkey for every post

Apple dictation is free and built in, but it can stop listening when you pause to think, it depends on settings that are easy to switch off by accident, and fixing a misheard word means going back and editing by hand.

Voice Keyboard Pro is a menu bar app for Mac. Click where you want the text, hold your hotkey, speak, and release. The text appears at your cursor, system-wide: in the Threads composer, in a reply, in your email and in every other app you use. The microphone stays live while you hold the key, so a pause to find the right word does not end the session. Like any dictation app, it puts text wherever focus is, and Threads still decides how long a post can be, so fixes 1 to 9 still apply.

A few features are useful beyond the post box:

• Smart Vocabulary is a personal dictionary with replacement rules, so names, product names and the handles you mention most come out written your way every time.
• Meeting Mode, with speaker detection and AI notes, captures a call or a meeting, so what you post about it afterwards starts from what was actually said.
• Calendar meeting detection notices when a meeting on your calendar is about to start.

On privacy, our servers store only operational pings. No audio and no transcript content is stored. There is a free tier with daily limits, and Pro is $4.99 a month or $34.99 a year. On iPhone, the same product is a custom keyboard with a built-in mic button, so you can dictate in any iOS app, the Threads app included.

Frequently asked questions

Does Threads have voice typing on a Mac?

No. The Threads website has no dictation button of its own. On a Mac you dictate with the dictation built into macOS or with a dictation app, and both deliver text to whichever field has keyboard focus.

Why does dictation work in TextEdit but not in Threads?

Almost always because no text box had the cursor, or because focus was somewhere else, such as the search field, another reply or a different post in a thread. Open the composer, click in the post box until the cursor blinks, then speak.

Why will Threads not let me post what I dictated?

The post is probably over the 500-character limit. Trim it, or add another post to the thread and move the overflow there. If the box looks empty, your words went into a different field.

How much can I say in one Threads post?

500 characters is roughly 80 to 100 words, which is about 35 to 45 seconds of speech at a normal pace. For anything longer, dictate it in a document and split it into a thread.

Can I fix a dictation mistake after posting?

Only for a short time. At the time of writing, Threads allows edits for a limited window after a post goes out. After that you delete the post and write it again, so read a dictated post before you publish it.

Does my browser need microphone permission for Threads?

Not for Apple dictation or a menu bar dictation app, because your Mac or the app does the listening. A dictation app needs Microphone and Accessibility permission in System Settings. Any microphone request from the Threads site itself is for its own media features.

What to do next

Run the 30-second TextEdit test, then work through the fixes that match what you saw. For most people it is fix 1 or fix 2: no text box had the cursor, or a different box did. If the words arrived and Post stopped working, it is fix 3. Whatever the cause, read a dictated post before you click the button, because on Threads the window for edits is short. And if you want dictation that works the same way in Threads, in your email and in every other app on your Mac, Voice Keyboard Pro has a free tier you can try today.