<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Vin Xu on Medium]]></title>
        <description><![CDATA[Stories by Vin Xu on Medium]]></description>
        <link>https://medium.com/@vinxu?source=rss-68e8e856aaee------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*VZ4Na7UvBQ97_m2d.</url>
            <title>Stories by Vin Xu on Medium</title>
            <link>https://medium.com/@vinxu?source=rss-68e8e856aaee------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 08:30:27 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@vinxu/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[I read somewhere that the average knowledge worker spends 28% of their workday reading.]]></title>
            <link>https://medium.com/@vinxu/i-read-somewhere-that-the-average-knowledge-worker-spends-28-of-their-workday-reading-f363e4af0c72?source=rss-68e8e856aaee------2</link>
            <guid isPermaLink="false">https://medium.com/p/f363e4af0c72</guid>
            <category><![CDATA[google-chrome-extensions]]></category>
            <category><![CDATA[text-to-speech]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[tools]]></category>
            <dc:creator><![CDATA[Vin Xu]]></dc:creator>
            <pubDate>Sun, 22 Mar 2026 13:42:28 GMT</pubDate>
            <atom:updated>2026-03-22T13:42:28.312Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="I Spent a Week Testing Every Free Text-to-Speech Chrome Extension and Most of Them Are Lying to You" src="https://cdn-images-1.medium.com/max/1024/1*z3sH16ZX44TzX89SlVnBdw.png" /><figcaption>I Spent a Week Testing Every Free Text-to-Speech Chrome Extension and Most of Them Are Lying to You</figcaption></figure><p>I read somewhere that the average knowledge worker spends 28% of their workday reading. Emails, Slack threads, docs, Jira tickets, whatever. Twenty-eight percent. I did the math on my own screen time last Tuesday and it was closer to 40.</p><p>So I figured — what if I just listened to half of it instead?</p><p>That’s how I ended up installing eleven different text-to-speech Chrome extensions in one week. My browser looked like a Christmas tree of little speaker icons. My coworker Sarah walked by, saw my extensions bar, and said “are you okay?” I</p><p>was not okay. But I learned things.</p><p>Here’s the thing nobody tells you about TTS extensions. They all say free. They all say natural voices. They all have screenshots showing someone peacefully reading a Medium article with headphones on. And then you install one, click the</p><p>button on a New York Times article, and it sounds like a GPS from 2009 telling you to make a U-turn.</p><p>I started with Read Aloud because it had 4 million users and a green play button that looked friendly. It works. I’ll give it that. You click, it reads. The voice selection is decent — you get Google’s voices, which sound fine for short</p><p>bursts. But I tried it on a 3,000-word Paul Graham essay and by paragraph four I wanted to throw my laptop into the Pacific. The voice has this cadence where every sentence ends the same way. Goes up slightly, pauses, starts the next one</p><p>exactly the same. It’s like listening to someone who learned English from reading instruction manuals. For a free extension with zero sign-up, though? Solid. I just couldn’t use it for more than five minutes at a stretch.</p><p>NaturalReader was next. The free tier gives you a couple of decent voices. The paid voices actually sound good — I tested the premium trial and was genuinely impressed for about three paragraphs. Then the trial ran out and it was back to</p><p>Robot Karen. The thing that annoyed me most was the UI. There’s this floating panel that takes up a quarter of the screen and doesn’t remember its position. Every. Single. Time. I opened a new page I had to drag it out of the way again. Maybe</p><p>I’m petty. I’m petty.</p><p>Speechify. Oh, Speechify.</p><p>Look, Speechify has raised something like $100 million in funding. Their marketing is everywhere. Snoop Dogg is involved somehow. The product is legitimately good — the voices are the best I’ve heard in any TTS product, period. But here’s the</p><p>part where I get frustrated. You install it, try it once, it sounds amazing, and then it tells you the free tier gives you — I’m not making this up — 500 characters per conversion. That’s like two paragraphs. That’s not even one email from</p><p>my PM. The premium is $139 per year. For reading web pages out loud. I mean, if you’re a heavy user and you can expense it, go for it. But calling yourself free and then limiting to 500 characters is the kind of thing that makes people write</p><p>angry Reddit posts.</p><p>Then someone on Hacker News mentioned CastReader in a thread about Kindle read-aloud tools and I figured why not, extension number seven, what’s one more.</p><p>I clicked install. Opened a long Ars Technica article about the M4 chip. Clicked the extension icon. And it just started reading. Good voice. Not Speechify-premium good, but genuinely natural — the kind where you forget you’re listening to a</p><p>computer after a couple of minutes. I went to make coffee and when I came back it was still going. No popup asking me to sign up. No character limit. No floating panel covering half the article. Just — reading. With this subtle highlight on</p><p>the current paragraph so I could glance down and know exactly where it was.</p><p>I texted my friend Jake, who’s a PhD student drowning in papers. “Try this.” He texted back twenty minutes later: “wait it read my entire 47-page PDF for free?? what’s the catch”</p><p>I kept looking for the catch. Used it every day for the rest of the week. Read Notion docs. Google Docs. A Wikipedia rabbit hole about the Ottoman Empire that lasted two hours. Even opened Kindle Cloud Reader and it read a chapter of a book</p><p>I’d been ignoring for months. No catch. No login wall. No premium upsell popup after three uses. I checked — it’s using some model called Kokoro and the processing happens in the browser, which I guess is how they keep it free.</p><p>Is it perfect? No. The voice doesn’t do dialogue well — it reads quotation marks the same way it reads everything else, so fiction with lots of character conversation gets flat. And the paragraph-level highlighting is nice but I wish it did</p><p>word-level like some of Speechify’s premium features. For non-fiction, though — articles, papers, documentation, blog posts — it’s the best free option I found. Not close.</p><p>Voice Out was another one I wanted to like. It has this clean interface and claims to work on Google Docs natively. It does. Sort of. It kept skipping headers and reading footnotes inline with the body text, which made a research doc sound</p><p>absolutely unhinged. The voices are okay. Not as natural as CastReader but better than Read Aloud. It’s free, truly free, which I respect. But the extraction — which text it decides to read and in what order — felt random on complex pages.</p><p>I tried two more that I won’t name because they were essentially the same extension with different icons. Same voices (browser built-in), same UI (floating play bar), same problem (sounds like someone reading a terms of service agreement at</p><p>1.5x speed). There’s a whole cottage industry of these. I think people just fork the same open-source code and slap a new name on it.</p><p>Here’s where I landed after seven days and eleven extensions.</p><p>If you’re willing to pay $139/year and you use TTS constantly — like, hours a day, for professional work — Speechify is the best product. The voices are unmatched and the word-level highlighting is excellent.</p><p>If you’re not paying $139/year (which is most of us), CastReader is the one to install. It’s free, the voice is good enough that you stop noticing it after a minute, and it works on basically everything including Kindle books in the browser,</p><p>which none of the others handled well. I’ve been using it daily for two weeks now and I haven’t hit a paywall, a limit, or a “subscribe to continue” modal. My reading-to-listening ratio has completely flipped. I read maybe 15% of my daily</p><p>content now. The rest I listen to while doing other things.</p><p>Sarah walked by my desk again yesterday. One extension in my toolbar this time. “You look better,” she said. I was listening to a 6,000-word feature about semiconductor supply chains at 1.3x speed while reviewing a pull request.</p><p>Twenty-eight percent of the workday, reclaimed.</p><p>castreader.ai — free, no sign-up</p><p>speechify.com — excellent but $139/yr</p><p>Read Aloud — solid free baseline</p><p>NaturalReader — good voices, annoying UI</p><p>Voice Out — promising but inconsistent extraction</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f363e4af0c72" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>