Mac Dictation Not Working in Bluesky? 10 Fixes That Work

Short answer: If Mac dictation is not working in Bluesky, open the composer and click in the post box until a cursor blinks, then dictate. On a Mac, Bluesky usually runs as a website with no built-in voice typing, so words go wherever focus is, and one post holds 300 characters.

You have a reply that deserves more than a few words, a thread you have been turning over all morning, or a photo that needs a proper description, and saying it would be far quicker than typing it. You press your dictation shortcut on your Mac, speak, and nothing appears. Or the sentence lands in the search box. Or the words arrive, the Post button stops responding, and the character counter tells you that you are over the limit.

Four facts about Bluesky on a Mac explain nearly all of it. First, Bluesky has 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 Bluesky page holds several separate text boxes, and the feed between them is not one of them. Third, a single post holds 300 characters, and people speak far faster than they type, so a dictated thought outgrows a post in well under half a minute. Fourth, you should not count on editing a post after it goes out. For most of Bluesky's history the only correction has been to delete the post and write it again, so the read-through has to happen before you click Post.

So most Bluesky dictation problems on a Mac come down to where focus was, how much you said, and what you did next. 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 Bluesky, start with our complete guide to Mac dictation not working instead. Bluesky updates its website often, so exact button names and positions may differ slightly from what you see.

First, which Bluesky are you in?

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

• The site in a browser tab. Bluesky at bsky.app in Safari, Chrome or another browser, with your feeds, profiles, search, notifications and the composer. This is what most people mean.
• An installed web app. Safari and Chrome can install a 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, with its own sign-in.
• A third-party client. Bluesky is built on an open protocol, so other developers make apps that read from it and post to it. Each one has its own composer and its own rules for the Return key, drafts and shortcuts, and most sign in with an app password rather than your main password.
• The composer. The window that opens over the page when you start a post or a reply, with the post box, buttons for images and other media underneath, and the Post button.
• Chat. Bluesky's direct messages. Each conversation has its own message box, and it follows chat rules rather than post rules.
• A second account. Bluesky lets you add more than one account and switch between them. A post goes out from whichever account is active in that window.

Every browser, browser profile and installed web app keeps its own sign-in, so the account active in Safari may not be the one in your Dock app. Knowing which window and which account you are in settles a good share of the confusion below.

How dictation reaches Bluesky 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. Bluesky 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 Bluesky's 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 Bluesky nor your browser needs anything extra, and there is no extension to install.

If your browser ever asks whether a site can use your microphone, that request has nothing to do with dictation. 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 Bluesky treats it exactly like typing. A sentence in the composer is a post. The same sentence in the search box 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 Bluesky, open the composer, click in the post box so the cursor blinks there, and dictate the same sentence. Do not click Post. Close the composer and discard the text when you are done.

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

Command-Z usually works in Bluesky's 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. Open the composer and click in the post box

Bluesky gives you more than one way to start writing. The New Post button in the sidebar opens the composer. In a narrow window the sidebar shrinks, and the button may turn into a small icon. The reply icon under a post opens the composer for a reply, with the post you are answering shown above the box. Opening a post takes you to its thread, where a reply prompt sits underneath, and clicking that opens the same composer. In every case the box is ready for words 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 an attached image, one of the media buttons or a setting under the box, 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 Bluesky page holds more text fields than it seems to: the search box, the composer, each post in a thread you are building, the description box for each image, a chat conversation, and the fields on your profile. 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 in the thread under the original. A quote puts the original inside a new post of your own, so it reaches your followers whether or not they follow that conversation. A new post has no link to either. The composers look alike, so check what is shown with the box before you speak.
• Posts in a thread. If you add more posts to a thread in the composer, 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 box becomes a search, and if a Return follows, a page of results replaces what you were reading. Press Command-A inside the box and delete. The browser's Back button returns you to the page you left.
• The small fields. Your display name, your profile description and the names of any lists or feeds you create 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 300-character limit

A single Bluesky post holds up to 300 characters. In ordinary English that is roughly 50 to 60 words. People speak at around 130 to 150 words per minute, so you reach the limit after about 20 to 25 seconds of talking. Typing rarely overshoots by much, because you watch the text grow as you go. Dictation overshoots the moment you have a second point to make.

The composer shows a small counter near the Post button. Once a post runs past 300 characters, the counter warns you, and Bluesky will not publish the post 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 300-character pieces. Say the whole thing, then remove what the post can live without.
• Turn it into a thread. Recent versions of the composer let you add another post below the first before you publish. Cut the overflow and paste it there. Each post in the thread has its own limit. If your composer does not offer that, post the first part, then reply to your own post with the rest.
• 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 Bluesky.

• In the composer, Return starts a new line. A post is not published until you click Post.
• In the search box, Return runs the search, and the results replace whatever you were looking at.
• In a chat, Return usually sends the message, 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 chat 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 handles, tags and links by hand

The composer watches what arrives and reacts to it. An @ sign opens a list of accounts to mention. A # sign starts a hashtag, which becomes a link other people can follow to see posts with the same tag. A web address becomes a link, and Bluesky may attach a preview card for it.

Dictated text lands as characters, so all of that still happens. While the account list is open, the Return and Tab keys can choose from it, so a dictated sentence containing an @ sign can open the list, and the next key press can select an account you never meant to mention. That person is notified. Dictation also struggles with this kind of text in the first place. A Bluesky handle looks like a web address, often a name followed by .bsky.social, or a domain the person owns, so dictation tends to write "dot" as a word or spell the name the way it sounds. A hashtag is often several words run together, and dictation spaces them out.

What to do:

• Say the sentence first, stop dictation, then type the @ yourself and choose the account from the list by clicking it.
• Type hashtags by hand, with no spaces inside the tag.
• Paste links after the text rather than dictating them, and check that any preview card is for the page you meant.
• 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.

6. Describe images in the alt text box, not the post

Bluesky puts a lot of weight on image descriptions, and dictation is the fastest way to write them. Each image you attach has its own description, opened from a small ALT button on the image. It is a separate box with a much larger limit than the post. If you click the button and start talking before the cursor appears in the description box, or the box closes and focus drops back into the post, your description ends up as post text and pushes the post over 300 characters.

Bluesky also has an accessibility setting that requires alt text before you can post. With it switched on, the Post button will not work until every image has a description. If Post refuses to work and your post is comfortably under the limit, look for an image without one.

• Click ALT, wait for the description box to open, click inside it, then speak. Close the box with its own button when you are done.
• Say what the picture shows in a sentence or two of plain description. Read it once, because names and numbers are where dictation slips.

7. Keep an unposted draft safe

Text you have not posted exists only in the window in front of you. Press Escape, click outside the composer or reload the tab, and the composer can close or ask whether to discard what you wrote. A browser that restarts for an update can take an unposted post with it, too. Treat the composer as a place to finish a post, not a place to keep one.

• For anything longer than a single post, dictate in TextEdit or Notes and paste the result into Bluesky.
• 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.

Do not plan on fixing it afterwards. For most of Bluesky's history a published post could not be edited, so the only correction was 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 four more things:

• The account. The picture beside the composer shows which account the post will come from. If you run more than one, look every time.
• The kind of post. A reply shows the post it answers. If you meant to start a post of your own, you are in the wrong composer.
• Who can interact. The composer has settings for who can reply to the post and whether others can quote it. Change them before you post if they are not what you want.
• The language. If your composer shows a post language near the bottom, check it when you dictate in a language other than your usual one, because feeds and filters use it.

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

A session can end while a tab sits in the background, and Bluesky may ask you to sign in again, with a confirmation code sent to your email if you have two-factor sign-in turned on. 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.

If you use a third-party client, it signs in with an app password that you create in Bluesky's privacy and security settings. A client that keeps asking you to sign in may be holding an app password that has since been deleted, so make a new one. When you create an app password, Bluesky asks whether it may be used for direct messages, so a client that cannot open your chats may simply have a password made without that permission.

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

On a Mac, Bluesky usually runs in a browser, so the browser is part of the problem space. Open Bluesky 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.

Check what the microphone can hear, too. Feed videos usually start muted, but a clip you have unmuted, or a video or podcast playing in another tab, reaches the microphone along with your voice. Dictation then types the other voice into your post or misjudges where your sentences start and stop. Pause it first. Safari and Chrome show a speaker icon on any tab that is playing audio.

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, Bluesky 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.

Bluesky quirks that look like broken dictation

• Post will not work. The post is over 300 characters, as in fix 3, an image is missing alt text while the setting requires it, as in fix 6, 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, or one of you has blocked the other. No dictation setting changes that.
• Your reply posted, but others say they cannot see it. Authors can hide replies on their own posts, and anyone who has muted you, or muted a word or tag you used, will not see it. Dictation did its job. The audience is the issue.
• You cannot start a chat with someone. Each person chooses who can message them: everyone, only people they follow, or nobody.
• 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 10.
• The post came from the wrong account. The words are right and the name above them is wrong. See fix 8.

Quick triage

• Nothing appears anywhere on Bluesky: 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. Fixes 2 and 6.
• Post will not work: over 300 characters, or an image needs alt text. Fixes 3 and 6.
• 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.
• The text vanished: the composer closed or the page reloaded. Fix 7.
• A mistake went public: delete the post and post it again. Fix 8.
• A third-party client keeps signing you out: replace its app password. Fix 9.
• Nothing works in any app: it is your Mac, not Bluesky. Fix 10.

Bluesky on a Mac versus on iPhone

The two behave differently enough that advice for one rarely transfers to the other. On a Mac, Bluesky is usually 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, Bluesky 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 Bluesky covers that side step by step.

The same logic carries over to the other text-first networks. If you post in more than one place, our guides to dictation not working in Threads on a Mac and X on a Mac cover their own limits and shortcuts.

A dictation workflow that suits Bluesky

Most adults type at around 40 words per minute and speak at 130 to 150. On Bluesky 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. 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 short paragraph, and read it before you post.
• Image descriptions. Click ALT, click into the description box, 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 dictating replies and quote posts, see our guide on how to dictate on Bluesky.

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 Bluesky composer, in a reply, in an alt text box, 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 Bluesky 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 people 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. Pro is $4.99 a month or $34.99 a year, and the monthly plan starts with a 3-day free trial. On iPhone, the same product is a custom keyboard with a built-in mic button, so you can dictate in any iOS app, the Bluesky app included.

Frequently asked questions

Does Bluesky have voice typing on a Mac?

No. Bluesky 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 Bluesky?

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

Why will Bluesky not let me post what I dictated?

The post is probably over the 300-character limit. Trim it, or move the overflow into a second post. If the post is short, check whether an attached image needs alt text. If the box looks empty, your words went into a different field.

How much can I say in one Bluesky post?

300 characters is roughly 50 to 60 words, which is about 20 to 25 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?

Do not count on it. For most of Bluesky's history, the only fix for a published post has been to delete it and post it again, so read a dictated post before you publish it.

Does my browser need microphone permission for Bluesky?

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, and nothing in the browser needs to change.

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 or fix 6. Whatever the cause, read a dictated post before you click the button, because on Bluesky a published mistake usually means deleting and starting again. And if you want dictation that works the same way in Bluesky, in your email and in every other app on your Mac, Voice Keyboard Pro's monthly plan starts with a 3-day free trial.