You want a Chrome extension that reads your Twitter feed to you. You've found Read Aloud, which is free and open source. You've also found Xeder, which costs $4.99. Which should you use?
The short answer: it depends on what you're reading. Let me explain.
| Feature | Xeder | Read Aloud |
|---|---|---|
| Cost | $4.99 one-time | Free |
| Best For | Twitter feeds | Articles, webpages, PDFs |
| Twitter Experience | Optimized, tweet-aware | Reads all page content |
| Voice Quality | Excellent (Google Cloud) | Good (cloud or browser) |
| Open Source | No | Yes |
| Chrome 14-sec Bug | Not affected | Affected with browser voices |
| Configuration Options | Simple, focused | Extensive, power-user friendly |
Read Aloud is a free, open-source Chrome extension that reads any text on any webpage. It supports cloud voices from Google, Azure, and Amazon, or you can use your browser's built-in voices. It's highly configurable and beloved by power users.
Let me give you a concrete example. Say you have a tweet like this:
With Read Aloud, you'd hear something like:
You get the content, but you also get all the metadata and UI elements. That's annoying for listening. It breaks the flow. You have to mentally filter out all the noise to get to the actual content.
Now imagine you're scrolling and there's a promoted tweet (an ad). Read Aloud doesn't know it's an ad. It just reads it like any other tweet. You can't tell where the ads are. Your listening experience is polluted with advertisements.
With Xeder, on the same tweet:
Just the content. No timestamps, no view counts, no buttons, no metadata. Clean, focused reading.
And for promoted tweets? Xeder skips them. You know you're hearing real tweets from people you follow, not advertisements.
Chrome has a known bug with its built-in text-to-speech: it cuts off after about 14 seconds. This affects any extension using Chrome's native TTS voices.
If Read Aloud is using browser voices (not cloud voices), it's limited by this bug. Long tweets or passages get cut off.
Xeder uses Google Cloud Text-to-Speech, which is not affected by this bug. You get complete, uninterrupted reading.
Read Aloud is highly configurable. You can choose between Google, Azure, or Amazon cloud voices, or use browser voices. If you want to tinker with settings and have lots of options, Read Aloud is the power user choice.
Xeder uses Google Cloud voices by default. You don't have to configure anything. It just works, and the voices are excellent.
Voice quality-wise, both are good. Google Cloud voices are slightly better than browser voices, but the difference is marginal.
Read Aloud is free. Xeder costs $4.99.
If you're on a strict budget, free wins. But $4.99 is less than a coffee, and it's a one-time purchase that specifically solves the Twitter problem.
Yes. Many people do. They use Xeder for Twitter and Read Aloud for everything else (articles, blog posts, documents, webpages). Read Aloud is better for general web content. Xeder is better for Twitter.
If you're using your browser to read long-form content and your Twitter feed, you can have both tools working for you.
Optimized for listening to your X feed. No ads, no noise, just your tweets. One-time $4.99.
Get Xeder on Chrome Web StoreWant a complete breakdown of all methods to listen to Twitter? See how to listen to your Twitter feed in 2026: every method compared.
Curious about the technical reasons why general TTS tools struggle with Twitter? Read why general text-to-speech extensions don't work well on Twitter.
Comparing Xeder to paid tools? Check out Xeder vs. Speechify.
Yes. If you configure Read Aloud to use Google, Azure, or Amazon cloud voices, you won't hit the 14-second bug. But you still get the problem of reading all page content (ads, UI, timestamps) instead of just tweets.
No, Xeder is not open source. If being able to inspect the code is important to you, Read Aloud is the better choice for that reason.
Read Aloud works by reading visible text on any website, so it's not dependent on Twitter's DOM structure. It will continue to work even as Twitter changes. However, it will also continue to have the problem of reading all page content, not just tweets.
Not really. Read Aloud doesn't understand what's an ad and what's a tweet. You could manually stop it when an ad plays, but that defeats the purpose of automation.
Xeder is a Chrome extension, so it works on desktop Chrome and mobile Chrome (if your Android browser supports extensions). Read Aloud also requires Chrome or a Chromium browser.
Read Aloud is free and will work, though with the limitations mentioned. Chrome's built-in TTS is also free but has the 14-second bug. $4.99 is the cheapest way to get a tool specifically designed for this task.
Xeder uses Google Cloud voices by default. Customization options are more limited compared to Read Aloud, which supports multiple cloud TTS providers. Xeder prioritizes simplicity over configuration.