Listen to Articles While Walking: Free Browser TTS for Your Phone

You don't need a read-it-later subscription, a podcast app, or an account anywhere to turn a long article into walking audio. A phone browser, the article text, and 30 seconds of setup are enough.

The whole workflow in five steps

This is the entire loop. Once you've done it twice it takes under a minute.

• Open the article on your phone. Use your browser's reader mode if it has one — Safari's reader, Firefox's reader, Edge's immersive reader. It strips the navigation, comments, and ads so you only copy the prose.
• Select all and copy. Long-press, tap "Select All", tap "Copy". On iOS the same gesture works inside Safari Reader; on Android the share sheet has a "Copy" target.
• Open Quick TTS in another tab. Paste into the textarea.
• Press play. On the first play of the session your iPhone or Android may need a single tap to unlock audio — that's an OS-level rule, not a Quick TTS quirk. After that first tap, every later play just works.
• Pocket the phone and walk. Use Bluetooth earbuds with a hardware pause button if you have them, so you don't have to unlock the screen at every crosswalk.

Why a browser tool beats installing another app

Read-it-later apps with built-in TTS are great if you do this every day. If you do it occasionally — a long Substack on the way to the train, a 6,000-word essay you bookmarked over coffee — the install-account-import-listen friction is the whole reason you never actually listen.

A browser tool collapses that to: paste, play. There is no account. There is no library to maintain. There is no app icon staring at you for the 20 days a month you don't use it. When you do want it, the URL is a bookmark.

What it sounds like on a phone

Mobile listening uses your phone's built-in voice — what the code calls Browser TTS. It's the same engine that powers VoiceOver and Talkback. Quality varies wildly by device:

• Recent iPhones ship with the "Enhanced" and "Premium" Siri voices — download one in Settings → Accessibility → Spoken Content → Voices. They're genuinely good, easily on par with paid TTS apps from five years ago.
• Recent Android phones use Google TTS, which has improved a lot but is still flatter than Apple's premium voices. Settings → System → Languages → Text-to-speech output lets you pick the engine and download high-quality voices for your language.
• Quick TTS on desktop additionally offers Kokoro HQ — a near-audiobook-quality neural voice that runs on your GPU. It's not yet practical on phones because mobile WebGPU support is still spotty and the model is big. On a laptop, it's the option to use; on a phone, you're stuck with the OS voice for now.

Practical tips that actually matter

• Bump speed to 1.15x–1.3x. Default speed feels slow once you've adapted. A 5,000-word longread runs roughly 35–40 minutes at 1.0x; at 1.25x it's a 30-minute walk.
• Strip the cruft before you copy. Reader mode is your friend. If the page doesn't trigger reader mode, paste the text into Quick TTS first and manually delete obvious junk (image captions, "Subscribe to my newsletter" boxes) before pressing play. Quick TTS reads what you give it; garbage in, garbage out.
• Use earbuds with hardware buttons. Pausing without unlocking the phone is the difference between "listened to a whole article" and "gave up at the first traffic light."
• Download the OS voice ahead of time. Premium Apple and Google voices need a one-time ~100MB download over Wi-Fi. Do it once at home, not on cellular.
• Mind the screen-lock setting. Some phones suspend audio when the screen locks aggressively. Settings vary; if playback cuts out in your pocket, lengthen the auto-lock interval or keep the tab in the foreground with the screen dimmed.

How this compares to dedicated read-it-later apps

Instapaper, Readwise Reader, and Matter all offer URL-saving plus built-in TTS. They're polished. If you process 5+ articles a day this way, one of them is probably the right tool — particularly Readwise Reader, which has the most natural voices in the category.

Pocket, the most famous of these, shut down in 2025. If you were a Pocket TTS user looking for a replacement, Quick TTS plus your phone's clipboard is the no-account, no-migration version of the same workflow.

Quick TTS wins for: occasional listeners, anyone who refuses another account, content from sources the read-it-later apps can't fetch (logged-in pages, internal company docs, manually-cleaned text), and people who don't want their reading habits in another vendor's database.

Limitations you should know up front

• No URL fetching. Quick TTS won't pull an article from a link. You paste the text yourself. That's a privacy choice (no server, nothing logged), not laziness — but it's a real friction point compared to "share to Instapaper."
• No queueing. One article at a time. Finish, paste the next one. There's no playlist.
• No sync across devices. Each session is local. If you start an article on your laptop, the phone won't know where you stopped.
• No background download for offline. Once the page is loaded and the OS voice is installed, audio rendering happens locally and works offline — but you have to have loaded the article text into the page while online first.
• Mobile voice quality is OS-dependent. If your phone's built-in voice sounds bad, that's the ceiling on mobile. Desktop has Kokoro HQ; mobile doesn't, yet.

Try it

Open Quick TTS on your phone right now. Paste any article you've been meaning to read. Press play. If the audio doesn't start on the first tap, that's iOS's audio-unlock requirement — tap play once more and it'll go.

For specific questions about voices, file formats, and what the AI engines can do, the FAQ covers them. The guide documents nine other use cases for the same tool. If you're looking at a long ebook rather than an article, the sibling post on free EPUB to speech covers the same workflow for full books. And if you want to know how Quick TTS stacks up against Speechify, NaturalReader, and the rest, the comparison page is honest about where each one wins.