How to Listen to Long X Threads Instead of Reading Them

Long threads are written to be scrolled through quickly, but plenty of them deserve real attention: a reporter's timeline of an event, a researcher walking through a paper, someone explaining how they fixed a problem at work. Listening is a good way to give them that attention when your eyes are tired, when you are doing something else with your hands, or when reading on a small screen is just hard work.

The catch is that a thread on X is surrounded by things you do not want to hear. Here is how to get a clean listen, from the quickest method to the most comfortable one.

Option 1: your device's built-in reader

Every major platform can read the screen aloud without installing anything.

• iPhone and iPad: Turn on Speak Screen in the Spoken Content section of the accessibility settings. Swipe down from the top of the screen with two fingers and the device reads everything it can see, scrolling as it goes. Speak Selection reads just the text you highlight.
• Android: Select to Speak, found in the accessibility settings, reads the item you tap or the area you select.
• Mac: The Spoken Content settings include a keyboard shortcut to read selected text in any app.
• Windows: Narrator is the full screen reader. For lighter use, Microsoft Edge has a Read Aloud option for web pages.
• Chrome: The Reading mode side panel can read an article aloud and highlights words as it goes, though it works better on articles than on the X timeline.

These tools are always available and need no setup beyond turning them on. Their weakness with threads is that they read what is on screen. That includes display names, handles, timestamps, reply and like counts, "Show more" links and the occasional ad. On a 30-post thread that can double the listening time.

Option 2: clean the text first, then listen

The approach this site is built around is to separate the two jobs. First get the writing out of X and away from the clutter, then listen to the result.

1. Open the thread on X in a browser and make sure all the posts are expanded.
2. Select from the first post to the last and copy.
3. Paste into the thread reader on the home page.

The reader removes names, handles, counters and buttons, takes out "1/" style numbering, and joins posts that were split mid-sentence back into normal paragraphs. Replies from other accounts are left out unless you switch that off. Then press play. You hear only the writing, and the current sentence is highlighted so you can glance at the screen and see where you are.

Nothing is sent anywhere. The speech comes from voices already installed on your device, so it works the same way on a plane as on Wi-Fi once the page has loaded.

Choosing a voice

Voices vary a lot between devices. A recent phone or laptop usually has several natural-sounding English voices; older systems may only have one or two robotic ones. A few pointers:

• Try two or three: Read the same paragraph with each. Some voices handle numbers and abbreviations better, others have a pace that suits long listening.
• Install more if you can: Both Apple and Microsoft let you download extra voices in the system speech or language settings. They then show up in browsers too.
• Watch for "online" voices: Some browsers offer voices that are generated on a remote server. They often sound better but need a connection, and the text you play is sent to that provider. Our voice menu marks these so you can choose a local voice if you prefer.

Finding the right speed

The default rate in most speech engines is close to the pace of an audiobook narrator. That is a good place to start. After a few sessions, most people find they can follow 1.2x to 1.5x comfortably. Experienced screen reader users often go far faster, but they built up to it over months.

Speed is not one setting for all threads. A personal story can run quickly. A thread full of figures, names or steps you might want to follow later is worth slowing down for. Pitch matters less, but a slightly lower pitch can make a fast voice easier on the ears during long sessions.

On this site, the plus and minus keys change the speed by a tenth while the voice is talking, so you can adjust without stopping.

Keeping your place

Losing your place is the main frustration with long audio. A few habits help:

• Use sentence skipping: Press J or the left arrow to go back one sentence when you missed something, L or the right arrow to skip ahead. That is much quicker than scrubbing through a recording.
• Click to jump: In the reading view, clicking a sentence starts reading from it.
• Stop at a paragraph break: If you need to leave, wait for the end of a paragraph. Paragraphs in the reading view usually match a complete thought from the writer.
• Save it: Export the thread as text or Markdown and keep it with your notes, so you can come back later without finding the thread again.

When listening is the wrong choice

Some threads do not survive being turned into audio. A thread that is mostly screenshots, charts or photos depends on the images, and if the writer did not add descriptions, you will hear the words around them without the point. Threads that quote other posts heavily can also get confusing, because the quoted text is not always copied along with the post. For these, read with your eyes, or listen to the text and look at the images separately.

Listening also makes it easier to drift. If the content matters, for work or for a decision, give it the same focus you would give a podcast you want to remember. The guide to writing posts that read well aloud looks at the same problem from the writer's side, and the screen reader guide covers listening to X with full assistive technology rather than a read-aloud tool.

Questions