# Heartheweb > Editorial content from Heartheweb (heartheweb.com). Articles, comparisons, reviews, landings and tools — multi-locale, written for human readers and machine-readable for AI agents. ## Articles ### Best ways to organize notes that you'll actually keep using URL: https://heartheweb.com/journal/best-ways-to-organize-notes > Why most note organization systems fail, what three approaches actually survive long-term, and how audio review changes the math on retrieval. The best ways to organize notes share one trait: they cost less to maintain than they save in retrieval time. That rules out most of what productivity blogs recommend. PARA works if you review your projects weekly. Zettelkasten works if you are writing a book. For everyone else - commuters, knowledge workers, people with 200 unsorted voice memos - the answer is a capture inbox, two or three folders, and a system that runs on search, not structure. ## The one question worth asking before you pick a system Ask yourself how often you go back to your notes. Not how often you intend to - how often you actually do. If the answer is "maybe once a month," you do not need a Zettelkasten. You need a searchable text file and a decent title convention. If the answer is "daily, I cross-reference research constantly," then yes, invest in links, backlinks, and a graph view. But most people answer "monthly" and spend a weekend building a system designed for "daily." The note organization space is full of solutions to the wrong problem. The real problem for most knowledge workers is not organization - it is retrieval. And search solves retrieval at near-zero maintenance cost. Most advice skips this completely: they treat organization as the goal and retrieval as the reward. Flip that priority and most of the complexity falls away. ## Three organizational approaches that hold up after six months There are dozens of methods. These are the three that people are still running nine months after they set them up. **The inbox-plus-two-folders approach** is the one most people actually stick with. Everything lands in an inbox first. Once a week, you spend ten minutes moving items into two buckets: active (things you will use again this month) and reference (things you might need someday). Archive aggressively. The system is boring. It works. **PARA** (Projects, Areas, Resources, Archives) is the most popular structured method and genuinely good for people whose work is project-heavy. It organizes by actionability, not by topic. A note lives where it is useful right now, not where it semantically belongs. The risk: PARA requires that you maintain an active project list. If you stop doing weekly reviews, your PARA structure becomes a folder of vague names within four weeks. Use it if you already have active project reviews as a habit; add PARA on top of that, not in place of it. **Zettelkasten** - atomic notes linked to each other, building a network of connected ideas - is optimized for writers, researchers, and academics. Nick Luhmann, the sociologist who developed it, wrote 70 books using his physical Zettelkasten of 90,000 index cards. If you are not writing a book or conducting long-term research, this is more system than you need. That said, the core habit - writing in your own words instead of copy-pasting - applies to every method and is worth extracting even if you skip the full apparatus. ## Folders vs. tags vs. links: a practical split The debate between folders and tags is mostly a false choice, but the right answer depends on how your brain retrieves information. **Folders** work for people who remember where they put things. They impose one canonical location per note, which keeps organization tidy. The cost: a note that belongs in two places sits in one and gets missed when you need the other context. **Tags** work for people who remember how they would describe something. A note can carry five tags and surface across five views. The cost: tag discipline degrades over time. You start with `#productivity`, add `#productivity-tools` three months later, split into `#tools-paid` and `#tools-free` when you go deep - and a year from now you have 40 near-identical tags with overlapping territory and no way to clean them up without reviewing every note. **Links** (the Obsidian model) work best when your notes are primarily ideas rather than information. Linking is high-signal when it represents a real conceptual connection, low-signal when it is just topical proximity. For most knowledge workers, the practical split is: broad folders (three to five, no subfolders), a handful of stable tags for filtering (`#to-review`, `#reference`, `#project-name`), and links used sparingly for genuinely connected ideas. Skip if you are still building the system: anything more than two levels of folder nesting. The overhead of deciding whether a note goes in `/resources/tools` or `/tools/resources` costs more attention than the organizational gain is worth. ![Overhead flat-lay of paper index cards organized into categorical groups on a wooden desk](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/heartheweb/2026-09/454942-inline1.webp) ## PARA is good - here is when to stop before the theory takes over PARA has a well-documented failure mode: people spend more time reading about PARA than running PARA. This is not a knock on Tiago Forte's work - it is a description of how productivity systems get adopted by people who enjoy the meta-level more than the execution. Useful PARA implementation, condensed: - Four top-level folders, exactly. Not "Projects" and "Active Projects" as separate folders. - A note goes in the most actionable folder available. The archive is for completed projects, not for "stuff I might need someday" - that is Resources. - The weekly review cadence matters more than the folder names. If you are not reviewing, the structure degrades regardless of how clean it started. Where PARA breaks specifically for note-takers: it was designed for project management and file organization. Notes often do not map cleanly to a project - an interesting observation from a podcast, a sentence that struck you mid-read. These are Zettelkasten material, not PARA material. The practical fix: run PARA for project-related notes, keep a flat inbox for observations and half-formed ideas. Do not force every captured thought into a project folder. ## The notes nobody reviews (and what to do about it) Here is the honest problem nobody in productivity content admits: most captured notes never get reviewed. They sit in a perfectly organized folder, correctly tagged, searchable, and completely unread. The solution is not better organization. It is a review habit with actual friction built in. A few approaches that hold up: **Spaced revisiting**: not flashcard-style, but a simple weekly pass - open your notes app, sort by random, open ten notes, spend 30 seconds with each. You will be surprised what surfaces and what connections form that were invisible when you first captured the note. **QUEUE: 5 notes to review this week** - put specific notes in a weekly list the same way you queue articles to read. Treat your own notes as reading material, not just filing material. The act of naming them to a queue changes your relationship to them. **Convert to audio**: this is where the review math changes most dramatically. If you have processed notes in text form - a book summary, a research synthesis, a set of highlights with your annotations - converting them to audio and listening during a commute or run is a fundamentally different kind of review than visual skimming. You absorb differently. The notes sitting in your inbox, never revisited, become material you actually consume. ![Person commuting on train with wireless earbuds, listening to audio content by the window](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/heartheweb/2026-09/2e042f-inline2.webp) ## Organizing for audio: what changes when you listen instead of skim Most note organization is optimized for visual scanning - you are looking for a heading, a bullet, a keyword. Audio review changes the constraints. Notes that work well as audio have: - Self-contained sentences. Fragments and bullets compress fine on screen but break as narration. A bullet like "- Key insight: attention is scarce" reads cleanly when you see it; heard through earbuds at 1.5x speed, it lands nowhere. - Clear section structure. A heading read aloud signals "new topic" crisply. Nested bullets three levels deep narrate as noise. - Summaries at the top, detail below. You can skip forward if the summary covers what you need; you cannot un-listen to a paragraph that was not useful. This is not an argument for abandoning compact notes. It is an argument for including a one-to-three sentence synthesis at the top of any note you want to revisit later. Five minutes of processing at capture saves a confused listening session six months from now. The habit that makes this concrete: when you close out a note, add a line at the top - "SUMMARY: what I actually took from this." If you cannot write the summary in two sentences, the note is not yet processed. It is still raw capture, which is fine - just do not route it to your review queue yet. ![Clean organized digital note workspace on a tablet in dark mode, stylus resting beside](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/heartheweb/2026-09/9a090b-inline3.webp) ## What to skip outright **Color coding without a defined key**: this is the most popular self-deception in note organization. You assign green to "important," yellow to "in progress," red to "urgent" - and within three weeks you cannot remember the scheme and the colors mean nothing. Skip color coding unless it maps to exactly two states with an obvious visual logic. **Daily notes as your primary navigation**: common advice in the Obsidian community is to use a daily note as your main workspace. This works for personal journaling but poorly for reference material. A meeting note from Tuesday lives in "2026-09-02," not in "meetings/Q3/product." Search handles this, but your folder structure becomes a calendar rather than a knowledge base - two different tools pretending to be one. **Tags with more than two levels of nesting**: `#work/projects/client/active` is a folder in tag clothing. Use folders for that. The tag is for cross-cutting labels that do not fit a hierarchy - `#to-review`, `#high-signal`, `#send-to-someone`. Keep the tag list short enough that you can recite every tag from memory. ## Before your next reading session The best ways to organize notes are not the most sophisticated ones. They are the ones you are still using nine months after you set them up. For most people: a single capture inbox, three broad folders, global search as primary navigation, and a weekly ten-minute triage. Everything else is optimization for a use case you probably do not have yet. If you are sitting on 200 unreviewed notes alongside a reading list that keeps growing, the organizational question is secondary. The retrieval question - how do you actually absorb the material you have already collected - is the one that changes your week. Audio review during a commute covers in 30 minutes what would take 90 minutes of distracted screen time, and the retention is measurably different. QUEUE: the notes already in your system. That is where to start. ## FAQ ### What is the simplest note organization system that actually holds up? A single capture inbox plus two or three broad folders - active, reference, archive. Combined with strong search and a weekly 10-minute triage, this covers the vast majority of note-taking use cases without requiring ongoing maintenance. ### Is the PARA method worth learning? Yes, if you already have weekly project reviews as a habit. PARA organizes by actionability rather than topic and works well for project-heavy work. It fails when the weekly review cadence lapses - the structure degrades quickly without it. ### Should I use folders or tags in my note-taking app? A hybrid works best for most people: three to five broad folders for major areas, plus a small stable set of tags for cross-cutting filters like #to-review or #reference. Avoid tag proliferation - a tag system you cannot recall from memory has already failed. ### Why do I never go back to my notes? Because most note systems are optimized for capture, not for retrieval. The fix is a deliberate review habit - a weekly queue of 5 to 10 notes to revisit - rather than a better organizational structure. You can also convert processed notes to audio and review them during a commute. ### What is Zettelkasten and who is it actually for? Zettelkasten is a method of linking atomic notes to build a network of connected ideas. It was developed by sociologist Niklas Luhmann, who used a 90,000-card physical system to write 70 books. It is well-suited for researchers and writers doing sustained long-term work. For most knowledge workers, it is more system than the use case requires. ### How do you organize notes for audio listening? Notes that work well as audio have self-contained sentences rather than fragments, clear section headings, and a 2-3 sentence summary at the top. Writing a summary line when you close a note takes five minutes and makes audio review much more useful months later. ### How many tags should I have in my note system? Fewer than you think. A good rule: if you cannot recite every tag in your system from memory, you have too many. Keep tags to cross-cutting labels that do not fit a folder - to-review, reference, send-to-someone, high-signal. Use folders for everything that maps to a clear category. --- ### Read Aloud Extensions in 2026: Honest Take for Commuters URL: https://heartheweb.com/journal/read-aloud-extension > Read aloud extensions work for one-off desk sessions. They break the moment you leave your laptop. Here is an honest breakdown of what to use, and when. The 7:22 Wellington to Johnsonville, 22 minutes. Four articles in the queue from yesterday. I opened the read aloud extension on my laptop, clicked the icon, pressed play, and walked out the door. By the time I reached the platform, the audio had stopped. A read aloud extension only runs inside the browser tab. The tab was on my laptop, at home, on my desk. That was 2024. That single interaction, that moment of misplaced confidence, is how I ended up rebuilding my entire reading workflow from scratch. A read aloud extension promises something real: you are already in the browser, you have a tab open, you press a button and it reads. For the 40-tab knowledge worker who cannot quite justify a dedicated app subscription, it sounds like the sensible minimum. Here is what it actually delivers, and where it quietly fails. ## What a read aloud extension does (and what it doesn't) The mechanics are simple. A browser extension injects JavaScript into the current page, passes the DOM content to a TTS engine (either the browser's built-in Web Speech API or a cloud service via the extension's own backend), and plays back audio through your speakers or headphones. No account required on the simpler tools. No extra app. Press the icon, press play. The six names that appear on every list in 2026: **Read Aloud** (the open-source one by Tao Lee, free, no account, available on Chrome and Firefox), **NaturalReader**, **Speechify Web Clipper**, **Talkie**, **TTSReaderX**, and **Polly for Chrome**. Each of them works. The question is: works for what, and for how long? Read Aloud by Tao Lee is free, ships with decent voices, and reads whatever text you select or the whole page. Talkie keeps processing local, nothing leaves your machine. Polly for Chrome pipes Amazon's neural voices into the browser. NaturalReader and Speechify bring their own proprietary voice models and, for the paid tiers, voices that hold up on narration-length content. For a single article, read once, at your desk, in the browser: any of these will do. The ceiling appears somewhere between the second article and the sixth. ![Laptop screen overwhelmed with dozens of open browser tabs](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/heartheweb/2026-09/ac0356-inline1.webp) ## The formatting problem every extension shares A browser page is not an article. It is the article, plus the site navigation, the cookie banner, the newsletter pop-up, the "related articles" block, four sidebar widgets, the footer with 30 links, and whatever inline ads the publisher serves. When you press play on a read aloud extension, you are asking it to parse all of that, not just the editorial content. The better extensions, NaturalReader and Speechify in particular, try to extract the main text automatically. They succeed most of the time. On a clean blog post: fine. On a dense magazine layout with pull quotes, annotated sidebars, and tabbed content: the extraction fails silently. The extension reads a paragraph, jumps to a caption, reads half a heading, then loops back to an ad. You do not always notice immediately. You realise something is wrong at minute four when a sentence makes no sense in context. The open-source Read Aloud lets you select text manually before pressing play, which is actually the more reliable approach. But it means every article is a manual step before you can listen. QUEUE: 0 in your mental counter of articles you will actually get through today. This is not a problem that a better algorithm fully solves. It is structural. Extensions see what the browser renders, which is the full DOM. Dedicated article-to-audio tools extract from the raw URL, parsing the actual article text from the HTML source, stripping the navigation chrome, and producing a clean transcript. The difference in fidelity matters over a 3,000-word piece where six interruptions break the thread completely. ## Voice quality and the eight-minute problem The browser's built-in TTS engine, the Web Speech API, is designed for short system messages. Navigation instructions. Alert notifications. A 150-word page translation. It is not calibrated for longform narration. By minute eight of a dense article, the prosody starts to degrade. Sentences that end with a subordinate clause get mispronounced at the junction. Quoted speech loses its cadence. The reader starts to sound like a flat transmission: words delivered at consistent pace without breath or variation. I tested this across four free extensions over a six-week period in late 2024, during a vision impairment that took me off screens entirely. The result was consistent: useful for the first half of an article, fatiguing by the second half. The paid extensions with proprietary voice models hold up significantly better. Speechify's premium voices and NaturalReader's Studio voices are trained on narration-length material. They are a real improvement over the default browser voices. They also cost $12 to $20 per month, require an account, and process your content on their servers, which matters if you read anything sensitive, confidential, or under embargo. Talkie's approach, local processing, privacy-first, is the right architectural decision. But the voice quality reflects that trade-off. It sounds like it is processing locally. For three paragraphs of a news article: acceptable. For 2,400 words of a long-form analysis: tiring. ## The cross-device gap: what happens when you leave the laptop This is the one that broke my system in 2024. Browser extensions run inside a browser. Chrome for Android and iOS has no extension support in the traditional sense. Firefox for Android supports a subset of extensions, Read Aloud is available, but the experience is uneven and not optimised for one-handed use on a moving train. Safari for iOS has no support for third-party TTS extensions at all. If you read on multiple devices (laptop at the office, phone on the train, tablet at home), an extension-based workflow forces you to restart from the beginning on each device. There is no reading position sync. There is no persistent queue. There is no private RSS feed that your podcast app can subscribe to and pick up where you left off. Every device transition is a manual reset. The 75-minute daily commute between Wellington and the city runs on a phone. The extension stays on the laptop. The phone needs a different solution: either a dedicated mobile app, or a tool that converts articles to MP3 files and exposes a private audio feed that any podcast player can access. That is a fundamentally different architecture from a browser extension, and once you have it, you stop needing the extension for anything except the occasional desk-based one-off. ![Smartphone audio player showing article playback in progress](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/heartheweb/2026-09/477bd2-inline2.webp) ## Three scenarios where extensions are the right call I do not want to dismiss the extension model entirely. There are three scenarios where it is the correct tool. **One-time reads on a single machine.** You have a long PDF or a dense report open in Chrome. You are at your desk for the next two hours. You want to listen while you clean up your inbox. You will not need this article again. An extension is perfect: immediate, no friction, no account required. Read Aloud (free, open-source) handles this without any setup time. **Privacy-sensitive or air-gapped content.** If you are working with documents that cannot leave your machine, anything under NDA, legal drafts, medical records, Talkie's local processing model is the only option that keeps your content off cloud servers entirely. Accept the voice quality trade-off. The privacy guarantee is worth it in those specific contexts. **Quick sampling before committing to the queue.** Before you add an article to your reading list, you want to hear the first three paragraphs to check whether it is worth 12 minutes of your commute. An extension click is faster than any full workflow. Use it as a preview and triage tool, not a primary reading tool. ## Signal / bruit: what actually holds up across the week If your reading practice involves more than one device, more than one sitting, or more than five articles a week, the extension model generates friction faster than it removes it. The cross-device gap alone breaks the workflow for any commuter. The formatting extraction problem loses you content on every non-trivial layout. The voice quality ceiling fatigues you on pieces that run past ten minutes. The alternative is a tool that converts articles to a private audio feed: subscribable in any podcast app, accessible on any device, with clean text extraction that skips the sidebars and banners. TRANSMITTING: format mp3, queue persistent, device any. That is the architecture that holds up across a 75-minute commute, a lunchtime walk, and a session on the exercise bike at 7am. Three articles absorbed in the time it took to make coffee is not an extension result. It is a workflow result. The extension is a shortcut that looks cheaper than it is because the real cost is friction across the week, not the monthly subscription line. Worth noting: for users who sometimes need reading support because screens are not always available, a persistent private feed that plays in any podcast client is also a more reliable tool than an extension that requires the original browser tab to remain open. The extension disappears when the tab closes. The audio feed does not. ## Before your next commute Pick the right tool for the actual context: - **Desk, one-off, no account**: Read Aloud by Tao Lee. Free, open-source, immediate. Tao Lee has maintained it since 2017 and it has over 2 million installs on Chrome. - **Privacy-critical content, stays local**: Talkie. No cloud, no account, no data leaves the machine. - **Best voice quality in a browser context**: NaturalReader Studio or Speechify Premium. Budget $12 to $20 per month and confirm they support your full device mix before committing. - **Multi-device commuter workflow with a persistent queue**: a dedicated article-to-audio service with private RSS output. That is where heartheweb plays, and it is a different category entirely from a browser extension. The 7:22 train has left the platform more than 400 times since I changed my setup. QUEUE: 4 articles this morning, 4 finished before the city stop. The extension icon on my laptop gets opened maybe twice a month now, for quick one-off reads at the desk. That is the right scope for it. ## FAQ ### What is the best free read aloud extension for Chrome? Read Aloud by Tao Lee is the strongest free option. Open-source, no account required, works on Chrome and Firefox, and has over 2 million installs. It reads selected text or full pages. Voice quality is basic but reliable for one-off desk sessions. If you need better voices without paying, TTSReaderX is a reasonable alternative. ### Can read aloud extensions work on mobile? Standard Chrome extensions do not run on Chrome for iOS or Android. Firefox for Android supports Read Aloud, but the experience is limited compared to desktop. If your reading happens on a phone during a commute, a dedicated article-to-audio app or a private RSS audio feed is a more reliable and persistent workflow than any browser extension. ### Why does my read aloud extension read ads and navigation instead of the article? Extensions read what the browser renders, which includes the full page DOM: navigation menus, sidebars, cookie banners, footers, and ads alongside the editorial content. Better extensions like NaturalReader and Speechify auto-extract the article text, but this fails on complex layouts. Selecting text manually before pressing play is the most reliable workaround. ### Is Speechify extension worth paying for? If you use it primarily at the desk for single sessions, the free tier often suffices. If you need higher voice quality for articles over 10 minutes, or cross-device access via the Speechify mobile app, the paid tier is a real step up. Budget around $12 to $20 per month depending on the plan. Check whether they offer a trial before committing. ### What is the difference between a read aloud extension and a dedicated TTS app? Extensions run inside the browser tab and stop when you close the tab or leave the machine. Dedicated apps maintain a persistent queue, sync reading position across devices, and typically offer cleaner text extraction that skips ads and navigation. For commuters or multi-device readers, a dedicated article-to-audio tool is considerably more reliable than any browser extension. ### Which read aloud extension respects privacy best? Talkie processes everything locally. No audio, no text, no reading data leaves your machine. It is the right choice for sensitive content like legal drafts or confidential reports. The trade-off is voice quality: local processing sounds noticeably more robotic than cloud alternatives. For non-sensitive material, cloud-based extensions offer a better listening experience. --- ### Personal assistant AI: what knowledge workers actually use URL: https://heartheweb.com/journal/personal-assistant-ai-knowledge-workers > Personal assistant AI has split into two distinct categories in 2026: tools that triage information and tools that execute tasks. Knowing which one you need changes which one you pay for. QUEUE: 47 articles unread. Reading time at current pace: 11 days. Personal assistant AI was supposed to fix the information overload problem, and in a narrow sense it has. But the fix is less obvious than the marketing suggests, and the tools that actually help are not always the ones getting the most attention. Here is what the landscape looks like after eight months of testing these tools against a serious reading practice. ## What personal assistant AI actually does in 2026 The category has fractured. In 2023, a personal assistant AI meant ChatGPT with a browser plugin. In 2026, it means at least five different things depending on who is selling it: - **Information processors**: Claude, ChatGPT, Perplexity, Gemini. You feed them documents, articles, long PDFs. They summarize, extract, compare, draft. The interface is conversational. They do not reach into your calendar unless you explicitly connect one. - **Task executors**: Lindy, Motion, Saner.AI. These connect to your inbox, your calendar, your project board. They file emails, schedule meetings, surface tasks before you ask. The interface is automation, not conversation. - **Reading-specific tools**: Readwise Reader, Omnivore with AI summaries, Matter. These focus on the consumption layer. They save, annotate, and try to surface what matters from your saved articles. - **Workspace-embedded assistants**: Notion AI, Linear Asks, Slack AI. These operate inside tools you are already in. They summarize a thread, draft a spec, answer questions about your notes database. - **General orchestrators**: Simular, Manus, and a handful of others that attempt to act as agents across all of the above. Most are still rough in practice. The mistake most professionals make is treating these as substitutes. They are not. A well-configured Lindy does not replace Claude. Claude does not replace a reading queue with audio output. Each layer does a different job. ![Smartphone showing a minimal article reading queue in terminal-style interface](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/accorata/2026-08/3cc330-image-inline1.webp) ## The tools worth knowing: a short list without the hype Five tools get most of the attention in 2026. Here is what they are actually good for: **Claude** (Anthropic, $20/month Pro) handles long-context work better than anything else tested. Feed it a 40-page PDF or a 6,000-word essay and ask it to identify the two strongest arguments and three factual claims worth verifying. The output is dense, accurate, and structured without being mechanical. For knowledge workers who read primary sources, white papers, or long-form analysis, this is the clearest use case. Weaknesses: no proactive behavior, no calendar integration on the base plan, and it still occasionally produces errors on citation-heavy material if you do not prompt carefully. **ChatGPT** (OpenAI, $20/month Plus, $30/month Team) remains the most capable general-purpose tool. It handles images, code, voice, web search, and file analysis in one product. For someone with varied tasks spanning writing, research, and visual review, the breadth is hard to match. The voice mode is genuinely useful on a commute for thinking through a problem out loud. It is not the right tool for deep single-document analysis; Claude holds that position. **Notion AI** ($10/month added to any Notion plan) is the strongest option if your working notes already live in Notion. It can search across your entire workspace, answer questions about notes you wrote six months ago, and draft new pages in your own writing style. The limitation is obvious: it only knows what is in Notion. If your research lives in PDFs scattered across a Downloads folder, it has nothing to work with. **Perplexity** (free tier available, $20/month Pro) sits between a search engine and an AI assistant. It is source-backed and cites URLs, which matters when accuracy is non-negotiable. For journalism-adjacent research, fact-checking, or building a sourced brief quickly, it is more reliable than ChatGPT for web-dependent queries. If you want background context on a topic before listening to a long article, Perplexity gives you a 200-word calibration in under 30 seconds. **Motion** ($49/month individual) is the task executor for calendar-heavy professionals. It reschedules automatically when meetings shift, protecting blocks for focused work. For people who manage their day around time blocks, the productivity gain is real. For readers who primarily need an information layer, it is overkill. ## Where personal assistant AI breaks down for serious readers The category has a structural blind spot: it is built for production, not consumption. Every major personal assistant AI is optimized to help you write faster, schedule smarter, or process incoming requests. The assumption is that your problem is output. But the knowledge worker problem is often the opposite: too much incoming information, not enough time to process it. The queue is not empty because you are not productive enough. It is full because the ratio of good content to available reading hours is completely broken. Personal assistant AI helps with one part of that problem: triage. Claude can read 10 articles for you and tell you which three matter. ChatGPT can summarize the key claims in a 5,000-word piece in 90 seconds. This is real value. But it does not solve the consumption problem. The working-through of an argument, the time spent with a well-made piece, the connection between one essay and something you read three weeks ago. Summarization compresses that. Sometimes compression is what you need. Often it is not. And none of these tools give you the article in audio. You cannot listen to Claude's summary on your morning run without copy-pasting it into a separate TTS app and losing the formatting, the structure, the sense of the original piece. ![Knowledge worker desk with wireless headphones, notebook and laptop for audio reading workflow](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/accorata/2026-08/d718b2-image-inline2.webp) ## The missing layer: from AI triage to audio consumption The workflow that actually works for commuters, runners, and anyone whose eyes are not always available is a two-step stack: - **AI triage**: Use Claude or ChatGPT to surface what is worth your full attention. A 10-minute conversation with your reading list can produce a ranked queue of three articles that deserve careful attention versus eight that can be skimmed or dropped. - **Audio consumption**: Send the worth-your-attention articles to an audio reading tool. Listen to them at 1.4x speed on the morning commute, or at 1.0x when the argument is dense enough to slow you down. This is where article-to-audio tools like heartheweb become part of the stack rather than a replacement for it. The AI assistant does not replace the reading. It decides what makes it onto the queue. The audio tool delivers it. For people with low vision or for situations where looking at a screen is not practical, this is not a productivity hack. It is the primary access path. The stack matters more, not less. === WORKFLOW === A typical session: 20 minutes on Sunday evening with Claude, reviewing 15 saved articles. Output: 4 that go into the week's audio queue. The rest get archived or summarized into a single note. Total listening time across the week: 3 hours 12 minutes at 1.3x speed, covering material that would have taken 6-plus hours of focused screen time. ## Building the stack: AI assistant and article-to-audio Practical setup for knowledge workers who consume primarily through audio: **Step 1 - Choose your triage tool.** Claude for long-form documents and primary sources. Perplexity when you need sourced context on a topic you know little about. ChatGPT when you have varied tasks and want one tool for everything. **Step 2 - Build a triage habit, not a triage system.** The elaborate Notion dashboard with AI-powered article scoring is not the answer. Fifteen minutes per week asking Claude which of your saved articles should go into the audio queue this week is the answer. Simple prompts produce more consistent results than complex workflows. **Step 3 - Send to audio.** Articles that pass the triage go into the audio queue. The narrator voice should be calibrated for long-form narration, not news snippets. The difference between a voice trained on podcast pacing and one trained on news-reader pacing is audible by the 8-minute mark of a 4,000-word piece. heartheweb uses a narrator-calm voice profile optimized for long reads, which is why the signal/bruit ratio stays high on dense arguments. **Step 4 - Capture on the move.** The insight you get while listening to the 14th paragraph of a good essay is not worth stopping for. The capturing habit is separate: a voice memo, a quick note on the return commute, a Readwise highlight if your tool integrates. ## Pricing reality: what you actually pay in 2026 A realistic knowledge worker stack: - **Claude Pro**: Long-form triage and document analysis: $20/month - **heartheweb**: Audio consumption of articles: from $9/month - **Readwise Reader**: Save and highlights sync: $7.99/month - **Perplexity Pro**: Source-backed research queries: $20/month Total for the full stack: $56.99/month. For those starting out: Claude's free tier allows 10-15 document analyses per day depending on length. heartheweb has a free tier for 5 articles per month. Readwise has a 60-day free trial. You can build a real stack for $0 for the first two months. Motion at $49/month is for a different problem set. If your days are not calendar-managed, it does not fit here. ## Before your next commute Personal assistant AI in 2026 is not one thing. It is a layer you add to an existing information workflow. The tools that work are the ones that do a specific job well: Claude for long-document analysis, ChatGPT for varied tasks, Perplexity when sources matter, Motion when your calendar runs your day. The part the category does not cover is what happens after the triage. The 3,500-word essay you decided is worth reading does not read itself. The commute is 22 minutes. Those are separate problems, and the tools that solve them are different. TRANSMITTING -> voice: narrator-calm -> format: mp3 -> queue: 4 articles -> estimated listen time: 1h 08m ## FAQ ### What is personal assistant AI? Personal assistant AI refers to software that uses language models to help manage information, schedule tasks, answer questions, and automate routine work. In 2026, the category splits between conversational information tools (Claude, ChatGPT) and proactive task executors (Lindy, Motion) that connect to your calendar and inbox. ### Which personal assistant AI is best for reading and research? Claude is the strongest option for analyzing long documents, PDFs, and complex articles. Perplexity is better when you need sourced web research. For integrating AI triage with an audio reading workflow, pairing Claude with an article-to-audio tool gives you both triage and consumption in the same day. ### Can personal assistant AI replace reading? Not without losing something. AI summarization compresses information efficiently but removes the time spent working through an argument. The more useful framing: AI triage decides what you read in full, then audio tools let you do that reading during time that would otherwise be dead, such as commutes, runs, or household tasks. ### How much does a personal assistant AI cost in 2026? Free tiers exist for Claude, ChatGPT, and Perplexity. Paid tiers run $20/month for Claude Pro or ChatGPT Plus. Task executors like Motion start at $49/month. A functional reading workflow stack costs $28-57/month depending on which tools you include. ### Does personal assistant AI work without a screen? Conversational AI tools like Claude require a screen for input and output. The audio layer is separate: article-to-audio tools convert the text and deliver it as MP3 or through a private RSS feed you can play in any podcast client. For those who need a screen-free workflow, the combination of AI triage and audio output is more useful than either alone. ### What is the difference between a personal assistant AI and a chatbot? A chatbot responds to a single query with no memory of your context. Personal assistant AI in 2026 maintains session memory, connects to external tools, and in the case of task executors, acts without prompting when it detects something that needs handling. ### Is personal assistant AI useful for low-vision users? The triage layer is screen-dependent, which limits its utility for low-vision users in its current form. The downstream benefit is real: once articles are queued for audio output, the consumption layer is fully hands-free and screen-free. Keyboard-accessible interfaces and voice-input options for the AI triage step are improving, but still uneven across tools. --- ### How Does AI Noise Cancellation Work: A Technical Guide URL: https://heartheweb.com/journal/how-does-ai-noise-cancellation-work > How AI noise cancellation actually works: the five-stage pipeline from microphone signal to clean audio, and which tool fits your workflow in 2026. How does AI noise cancellation work? The core is a trained neural network running on your microphone signal, processing 50 frames per second. Each frame is analyzed for the probability that a given frequency bin contains speech versus noise. The model has seen that pattern before -- millions of times in training. It applies a suppression mask and reconstructs clean audio, all in under 30ms. Unlike older approaches that cut fixed frequency ranges, the model handles moving noise: dogs, HVAC ramp-ups, passing traffic. ## How traditional noise filters fell short Old-school noise reduction worked by sampling the room during a silence period -- typically the first second of a recording -- and subtracting that noise profile from everything that followed. Spectral subtraction, in technical terms. It worked in controlled recording environments where background noise is constant: a faint hiss, an HVAC hum locked to a fixed frequency. The problem: real noise does not stay constant. A colleague walks behind you. A dog starts barking halfway through your presentation. A truck passes the window. Spectral subtraction either undercuts the voice or leaves the new noise untouched, because the noise profile it built is already stale. Wiener filtering improved on this. Using statistical models, it estimates the optimal filter shape for a given noise condition -- not just subtracting but weighting each frequency component by an estimate of how much noise it contains. Better than raw subtraction, but still model-based: the algorithm has no prior understanding of what a human voice sounds like. It only knows what the noise looked like when it started measuring. What changed with deep learning is that the model is no longer guessing at noise from first principles. It has heard it before -- in thousands of hours of paired clean and noisy training recordings. ## The five stages of an AI noise suppression pipeline Understanding the pipeline helps explain why a dedicated tool like Krisp outperforms the built-in suppression in Zoom or Teams on difficult noise types. The pipeline runs entirely in real time, on every 15ms of audio your microphone sends. **1. Frame segmentation.** Your microphone stream is split into overlapping frames of 10-20ms each. Small enough to maintain real-time responsiveness -- a 15ms frame budget means 66 passes per second. Large enough to contain meaningful phoneme information. **2. Frequency domain conversion.** Each frame is run through a Short-Time Fourier Transform (STFT), converting it from a time-domain waveform into a spectrogram: a representation of which frequencies are present at what intensity. This is the form the neural network actually operates on. The spectrogram makes visible what the time-domain signal hides -- the distinct frequency shapes of speech versus noise. **3. Inference.** The trained model examines the spectrogram and estimates, for each frequency bin, the probability that this component is speech versus noise. The architecture varies by tool. RNNs (Recurrent Neural Networks) maintain context across frames -- they carry a memory of what the previous 300ms sounded like, which helps classify ambiguous moments correctly. CNNs analyze spectral patterns across frequency bands in parallel. Most production systems combine approaches. Krisp-class models run roughly 10-30 million parameters -- compact enough to run on CPU in real time, large enough to generalize to noise types not present in training data. **4. Masking and suppression.** The model outputs a gain value between 0 and 1 for each frequency bin. Bins classified as noise get their gain reduced. Voice-identified bins pass through at full strength. The masking is continuous, not binary: a bin that is 70% likely to be noise gets gain reduced proportionally, which preserves the edge of a high-frequency consonant that happens to live near a fan's spectral peak. **5. Reconstruction.** The masked spectrogram is converted back to a time-domain audio signal via the inverse STFT. This is the clean audio your call app receives. Total latency: 10-50ms from the original microphone signal -- imperceptible on a call. ![Neural network audio waveform visualization on a studio monitor screen](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/heartheweb/2026-08/07ea74-image-inline1.webp) ## Why on-device processing is not optional Cloud-based noise suppression exists -- Adobe Podcast Enhance is the clearest example -- and it produces excellent results on recorded audio. The trade-off is structural: your audio has to travel to a server and back, adding 100-200ms minimum per round trip. That latency is acceptable for post-production work. On a live call, 200ms of added delay makes conversation feel like a satellite link, with the half-second pauses that follow. Krisp processes everything locally, on your CPU. The model is compact enough to run in real time on a standard laptop: roughly 5-15% CPU overhead on a modern chip (Apple M-series, Intel 12th gen or later). On older machines, or during long calls with simultaneous screen sharing, the load is more noticeable. The audio never leaves your device -- a point enterprise procurement teams care about when reviewing GDPR compliance and data processor agreements. NVIDIA Broadcast takes a different path: it runs the inference on your RTX GPU rather than CPU. Near-zero CPU overhead and strong suppression quality, but it requires NVIDIA RTX hardware. If you are on a Mac or a Windows laptop without an RTX card, this option is not available. === SIGNAL / BRUIT === The relevant question for most knowledge workers: is the suppression good enough that your callers stop commenting on your background noise? For the majority of home-office scenarios -- keyboard clicks, air conditioning, street traffic -- both Krisp and NVIDIA Broadcast clear that bar within the first week of use. ## Krisp, NVIDIA Broadcast, and Adobe Podcast: what each gets right **Krisp** runs as a virtual audio device, sitting between your physical microphone and your call application. You select "Krisp Microphone" in Zoom, Teams, Discord, Loom, or any tool that lets you choose an input source, and the model processes your outgoing audio before it reaches the app. The bidirectional mode also applies suppression to incoming audio from other callers -- filtering the noise behind a colleague's voice before it reaches your ears. Free tier: 60 minutes of noise cancellation per day. Pro: $8/month on annual billing, $16/month month-to-month. **NVIDIA Broadcast** integrates into the NVIDIA app and also exposes a virtual microphone. No usage limits, no subscription -- free if you own an RTX card. The suppression is aggressive and performs well on stationary noise types (HVAC, traffic, AC hum). On voices carrying a high density of fricatives (s, sh, f sounds), maximum suppression occasionally introduces an "underwater" quality -- a known artifact of aggressive mask application in high-frequency ranges. **Adobe Podcast Enhance** is not real-time: you upload a recording file and download the processed version. It applies a richer enhancement pipeline, using generative components to reconstruct frequency ranges that background noise had degraded. For podcast production, recorded interviews, and voice-over work, it is the strongest post-production option available as of mid-2026. It uploads audio to Adobe's cloud, which matters for confidential recordings. **Built-in Zoom and Teams suppression** uses lighter models designed to minimize CPU impact across the broadest hardware base. On sustained, stationary noise types they perform well. On transient noise -- a sudden cough, a door slam, a child shouting -- they lag one to three frames before the model adapts, and that gap is audible. ## The noise types that still beat the models **Simultaneous speech.** A voice talking in the background is extremely difficult to suppress without degrading the target voice, because the model sees two sources with similar spectral characteristics. Background voice cancellation is a distinct feature from noise cancellation -- and better in 2026 than in 2024 -- but it is still not reliable when the background speaker is at comparable volume to you. **Music.** Structured audio -- a song playing from a speaker behind you -- has harmonic patterns the model may classify as speech. The result is partial suppression that sounds like muffled radio. Most tools have a dedicated music suppression mode, but reduction is partial rather than elimination. **Room reverb.** Acoustic echo (your speaker audio picked up by your microphone) is handled by dedicated echo cancellers. Room reverb on a voice recorded in a bare, hard-walled apartment is more resistant: the reflected energy is baked into the same frequency space as the direct voice, and suppressing it suppresses voice detail at the same time. **Sudden broadband transients.** A fire alarm, a burst of applause, a sharp door slam. The model processes in 15ms frames, so the first one or two frames of a loud transient pass through before the mask adapts. At maximum suppression, recovery from a transient sometimes produces a brief artifact. ![Remote worker on a video call wearing a USB headset in a home office](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/heartheweb/2026-08/22bf78-image-inline2.webp) ## The metrics worth paying attention to **PESQ (Perceptual Evaluation of Speech Quality)**: a 1-5 scale estimating how a human listener would rate audio quality. A clean studio recording scores around 4.5. Krisp-class suppression at its best lands around 3.8-4.2 on stationary noise types. **STOI (Short-Time Objective Intelligibility)**: measures how understandable the processed speech is, on a 0-1 scale. Good suppression keeps STOI above 0.85. **SNR improvement in decibels**: how much noise the system removed relative to the input signal. A 15-20dB improvement is typical of Krisp-class tools on stationary noise. Transient noise achieves lower consistent improvement. These numbers matter if you are selecting a tool for a contact center or a podcast production pipeline. For a knowledge worker on three daily video calls, the practical test is simpler: run Krisp for two weeks in your real environment, check whether your callers stop commenting on background noise, and decide from there. ## Before your next call The mechanism: a trained model running local inference 50 times per second on the frequency content of your microphone stream. It applies a gain mask, reconstructs clean audio, and delivers it to your call app -- all within one phoneme's duration. Krisp at $8/month is the practical starting point for knowledge workers on non-NVIDIA hardware. If you are on an RTX machine, NVIDIA Broadcast at $0 is the natural first comparison. For recorded audio going through post-production, Adobe Podcast Enhance handles what real-time tools cannot. What none of them fix is a bad microphone signal. Noise suppression works on noise around the voice, not on a voice that was poorly captured to begin with. A $35 USB condenser in a quiet corner will outperform a $5 headset running the best AI suppression available. SIGNAL ACQUIRED. NOISE FLOOR: -62dB. QUEUE: clear. ## FAQ ### Is AI noise cancellation the same as active noise cancellation in headphones? No. Active noise cancellation (ANC) in headphones is hardware-based: microphones sample external sound and the drivers produce an anti-phase signal to cancel it acoustically before it reaches your ears. AI noise cancellation is software-based: a neural network processes the digital microphone signal before it reaches your call app. The two can work together -- an ANC headphone plus Krisp -- but they solve different problems. ### Does Krisp work on Mac? Yes. Krisp runs natively on macOS and Windows as a virtual audio device. You select Krisp Microphone in any app that lets you choose an input source. The Apple Silicon build runs efficiently on M-series chips with roughly 5% CPU overhead on a modern Mac. ### Does AI noise cancellation slow down my computer? On modern hardware (2021 or later), the CPU overhead is 5-15% during active processing. On older machines or during long calls with simultaneous screen sharing, the load is more noticeable. NVIDIA Broadcast offloads processing to the RTX GPU, bringing CPU overhead close to zero -- but requires NVIDIA RTX hardware. ### Can I use Krisp with Discord, Zoom, and Teams at the same time? Yes. Krisp acts as a virtual microphone at the OS level. Any app that lets you select an audio input will see Krisp Microphone as an available source. You configure it once and all apps use it. Switching between apps works without any additional setup. ### Does Krisp send my audio to the cloud? No. Krisp processes audio entirely on your device. The neural network model runs locally, and your audio stream never leaves your machine. This is a significant difference from Adobe Podcast Enhance, which uploads audio to Adobe's cloud servers for processing. ### Why does my voice sound muffled after noise cancellation? Over-suppression occurs when the model applies too aggressive a mask to frequency bins shared by both your voice and the background noise. Most tools have a suppression intensity slider -- reducing it from maximum usually restores voice clarity. It can also indicate a poor microphone placement or a very high ambient noise level that forces the model into aggressive mode. ### What is the difference between noise cancellation and echo cancellation? Noise cancellation removes ambient background sounds from your microphone signal -- HVAC, traffic, keyboard clicks, crowd noise. Echo cancellation removes your outgoing speaker audio that your microphone picks up, preventing your call partner from hearing their own voice delayed. Both features are present in Krisp Pro. Zoom and Teams handle echo cancellation natively; their noise suppression is where third-party tools add measurable value. --- ### Text to Speech for Studying: What Actually Holds Up URL: https://heartheweb.com/journal/text-to-speech-for-studying > Text to speech for studying works, but only when the content type matches the tool. A practical breakdown of what holds up on academic material. Text to speech for studying is straightforward in theory: pipe your assigned reading through a narrator voice, listen while commuting or running, absorb 40 articles in the time it used to take you to read four. In practice, the gap between what TTS marketing promises and what happens when you load a 60-page textbook PDF into one of these apps is large enough to make most people abandon the experiment by the second week. I have used audio reading tools since 2014 and switched to audio full-time in 2024 during a project that made screen time difficult for several months. Here is what I found when I applied them to study materials specifically: not news articles or newsletters, where they work well, but the denser, citation-heavy content that students and researchers actually deal with. ## Your PDF is where most TTS apps fall apart The problem is not voice quality. On a 600-word news article, most TTS narrators sound reasonable. Load a chapter from a biochemistry textbook or a 25-page legal case summary and several things break. **Citation debris.** The narrator reads every citation bracket aloud. On a sentence like "the mechanism was first described in 1987 [14] and later confirmed [15, 16, 18]" you hear "the mechanism was first described in nineteen eighty seven bracket fourteen bracket and later confirmed bracket fifteen comma sixteen comma eighteen bracket." The information is still in there, but the cognitive cost of filtering that noise while following an argument is significant. **Footnote interruption.** Apps that parse PDFs sequentially pull footnotes mid-paragraph because that is where they appear in the file structure. A paragraph loses coherence when the footnote text fires inside the sentence it is annotating. **Formula and table handling.** Any quantitative content gets narrated as a string of symbol names, for instance "x sub i equals mu plus sigma sub i", or silently skipped depending on the parser. Either way, the load-bearing material in a technical chapter either becomes noise or disappears. **Header and section label repetition.** Section numbers, figure captions, and running headers inject into the audio stream. If a document uses numbered subsections throughout, the narrator says those numbers every time. Not every app handles all of these equally badly. The ones that perform best on academic content have custom PDF parsers that strip citation brackets, suppress footnotes to a secondary track, and skip figure captions. That is a specific engineering investment, and most consumer TTS apps have not made it. ![Close-up of academic PDF on tablet with footnotes and citation markers, where TTS voice quality gets tested](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/heartheweb/2026-08/dd281e-inline1.webp) ## What the research actually says about audio versus reading A 2016 study by Rogowsky, Calhoun, and Tallal tested 91 college-educated adults in three conditions: digital audiobook, e-text, and dual modality (listening and reading simultaneously). The material was a chapter from *Unbroken* by Laura Hillenbrand. The result: no statistically significant difference across the three conditions in comprehension at the time of testing or two weeks later. That is [the source](https://journals.sagepub.com/doi/10.1177/2158244016669550) most often cited when TTS companies claim audio is as good as reading. It is a real, peer-reviewed result. But it used narrative non-fiction, not a biochemistry chapter, not a legal contract, not a mathematics textbook. Material structure matters for what the research actually shows. The study tells you that your brain does not prefer one modality over the other for absorbing a story. It does not tell you that TTS handles structured academic content well. That is a separate question with a different answer. The practical signal here: TTS is not a shortcut for studying. It is a format shift. Used correctly on the right content, it processes roughly the same amount of information your eyes do. Used incorrectly, on the wrong material type or at the wrong speed, it processes less. ## Speed traps: why 1.8x works for news and stalls on a textbook The commuter use case and the study use case want different things from speed. On a morning news article, 1.8x feels comfortable after three or four sessions. Your brain fills in gaps, you know the genre, the vocabulary is familiar. You absorb maybe 80 to 90 percent of what you would at normal reading speed, and the trade-off is fine. On an introduction to organic chemistry chapter, the vocabulary is unfamiliar, the argument is load-bearing, and missing one sentence changes whether the next five make sense. At 1.8x you are not reading fast. You are skimming audio. The cognitive buffer fills, and the net retention from a 30-minute listening session may be lower than if you had read 12 pages slowly and retained them fully. The practical adjustment: study material at 1.0x to 1.2x for the first pass, especially on unfamiliar topics. Use higher speeds for review sessions where you already know the structure of the argument. This follows the same logic as re-reading: the second pass of a familiar chapter at 1.6x is genuinely efficient. The first pass on new material is not. ## Reading while listening: the dual modality edge The Rogowsky study included a dual modality condition. The finding was that combining audio and visual input was comparable to, not significantly better than, either alone. But practitioners report something that study design could not capture: dual modality reduces attention drift. When you are only listening, distraction is easy to miss. A sentence goes by while you think of something else, and unlike with a physical text, there is no visual evidence that your attention wandered. You do not notice the gap. When you are reading along with the audio, the visual anchor and the audio stream create two synchronized inputs for the same content. Attention drift is caught faster. When the audio gets ahead of your eyes, you notice within a second or two. This is not a memory advantage. It is an attention management advantage, and for anyone who has sat in front of study material for 45 minutes and retained almost nothing, that is worth understanding. ![Person with over-ear headphones reading on laptop in morning light, dual modality study session](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/heartheweb/2026-08/164600-inline2.webp) ## Three tools that hold up on academic material **heartheweb** handles article-to-audio cleanly on long-form content: essays, journalism, Substack pieces, newsletter archives. For studying, it is strongest on narrative and analytical material rather than structured academic PDFs. If your reading list runs toward research journalism and long-form analysis rather than textbooks, it fits the workflow well. The narrator voices hold up past 2,000 words without the prosody collapsing. Private RSS integration means you can queue reading list items from multiple sources without switching apps. $8 per month, or $6 per month on annual billing. **Readwise Reader** is the strongest option for academic workflows where annotation is part of studying. It handles PDFs with reasonable fidelity, syncs highlights to Obsidian or Notion automatically, and its audio mode reads the full document rather than a reformatted extract. The audio quality on dense material is functional without being exceptional. At $7.99 per month, it is one of the better integrated reading and audio tools for students who annotate heavily. **Speechify** has the broadest mobile integration and the most polished consumer experience. For students moving across multiple device types during a study session, that cross-platform consistency matters. On academic PDFs, citation handling is better than most apps: it suppresses many bracket sequences rather than narrating them. Voice quality on long content starts to flatten around the 15 to 20 minute mark on some narrator options. At $11.99 per month, it is the most expensive of these three. Skip: NaturalReader is fine for shorter documents but degrades noticeably on anything over 8,000 words. Google's built-in TTS is free but has no PDF parsing intelligence whatsoever, reading every header, footnote, and page number as part of the main body. ## When to skip TTS and just read Two cases where TTS makes studying slower, not faster. **Math-heavy content.** Any chapter where equations carry the argument is a text where listening means losing the structure. The narrator cannot render a differential equation into meaningful audio. You hear a string of symbol names in order, which is not how mathematical reasoning works visually. Use TTS for the explanatory prose paragraphs around the equations. Use your eyes for the equations themselves. **First encounter with a new conceptual framework.** The first time you meet a concept, whether that is Kuhn on paradigm shifts or the first chapter on a new statistical method, you need to be able to stop, reread, and sit with the idea. Audio moves at a fixed pace and does not let you linger. Reading does. Reserve TTS for material you are consolidating, not material you are encountering for the first time. Signal / bruit check: if you finish a 40-minute session and cannot summarize what you heard in three sentences, the modality was wrong for that material. ![Notebook with handwritten study notes next to smartphone showing audio waveform, active listening workflow](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/heartheweb/2026-08/07a13a-inline3.webp) ## Before your next study session Text to speech for studying works when the content type and the tool match. Narrative non-fiction, analytical essays, journalism, review papers in familiar fields: these run well through a narrator at moderate speed and deliver genuine time value. Dense technical first encounters, math-heavy chapters, and documents with embedded citation strings: these are harder territory where reading remains faster. The apps that handle academic material best have made specific investments in PDF parsing, not just voice quality. Voice quality is the easier engineering problem. Handling the structural debris of an academic document, the citation brackets, the footnote injections, the section numbers, without routing it into the main audio stream is the less-discussed problem. It is also the one that determines whether a 40-minute session was worth the headphones. QUEUE: 3 articles loaded. Narrator: calm. Speed: 1.1x. Start. ## FAQ ### Does text to speech actually help with studying or is it a distraction? For narrative and analytical content, including essays, journalism, and review papers in familiar fields, TTS delivers comparable comprehension to reading. For first encounters with dense technical material or math-heavy chapters, reading is more effective. The mode works; the content type has to match the format. ### What speed should I use when studying with text to speech? Use 1.0x to 1.2x for the first pass on unfamiliar material. Reserve 1.6x to 1.8x for review sessions where you already know the argument structure. Going fast on new technical content means skimming audio, not studying, and retention drops noticeably. ### Can TTS apps read academic PDFs and textbooks accurately? Most cannot handle academic PDFs well. Common failure modes include reading citation brackets aloud, injecting footnote text mid-paragraph, and dropping or garbling mathematical notation. Apps with custom PDF parsers built specifically for structured documents, like Readwise Reader or Speechify, do significantly better than generic TTS tools. ### Is it better to listen and read at the same time when studying? The dual modality approach does not improve comprehension scores significantly in controlled studies, but it reduces attention drift in practice. When audio and visual are synchronized, you notice when your attention wanders within a second or two rather than several minutes later, which is the real benefit for study sessions. ### How much does a good TTS app for studying cost? Readwise Reader at $7.99 per month is the strongest option for students who annotate and sync highlights. Speechify at $11.99 per month has the widest cross-device support and better citation handling on PDFs. heartheweb at $8 per month or $6 per month annual is strongest on long-form articles and analytical content rather than structured textbooks. ### What types of content should I avoid using TTS for when studying? Skip TTS for math-heavy chapters where equations carry the argument, since narrators cannot render formulas meaningfully. Also avoid TTS for the first encounter with an entirely new conceptual framework, where you need to stop, reread, and process slowly. TTS works best on material you are consolidating, not encountering for the first time. --- ### How Does AI Transcription Work: From Waveform to Text URL: https://heartheweb.com/journal/how-does-ai-transcription-work > AI transcription breaks speech into phonemes, maps them to words, and delivers a transcript in minutes. Here is what happens inside each step and where the accuracy ceiling actually sits. How does AI transcription work? It converts spoken audio into written text by chaining two specialized models: an acoustic model that reads the sound waveform as a frequency map and extracts phoneme sequences, and a language model that assembles those sequences into coherent words, sentences, and punctuation. On clean English audio -- a single speaker in a quiet room -- modern systems reach 95-99% accuracy and return a transcript within minutes. On real-world recordings, meetings with crosstalk and calls with background noise, accuracy drops to 85-92%, which is still fast enough and cheap enough that hybrid AI-plus-review workflows make more sense than full human transcription for most knowledge-worker use cases. ## The six steps from sound to text The pipeline is consistent across services, even if the underlying models differ: - **Audio capture** -- the file is ingested (uploaded or streamed live) and normalized to a format the acoustic model can process. - **Spectrogram extraction** -- the raw audio waveform gets converted into a spectrogram: a frequency-over-time representation showing which sound frequencies are active at each moment. - **Phoneme mapping** -- the acoustic model identifies phonemes, the smallest units of sound, from the spectrogram. A word like "thirty" resolves into something like /TH-ER-T-IY/ before it becomes text. - **Language modeling** -- a language model takes the phoneme sequence and resolves it into words, using context to fill in ambiguities. "The new report" versus "the knew rapport" gets decided here, not in the acoustic step. - **Speaker diarization** -- if the recording contains multiple voices, a separate model segments the transcript by speaker cluster. Each segment gets a label: Speaker A, Speaker B. - **Post-processing** -- punctuation, capitalization, and (in many services) domain-specific corrections are applied. The transcript is delivered, typically with timestamps at the word or sentence level. Steps 1-3 take milliseconds per minute of audio. Steps 4-6 are where quality diverges between services. ![Audio waveform converted into text output - AI speech recognition visualization](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/heartheweb/2026-08/e9b2b1-img-1.webp) ## The acoustic model: reading sound as a spectrogram The acoustic model does not "hear" the recording the way a human does. It reads a spectrogram -- a heatmap where the horizontal axis is time, the vertical axis is frequency, and color intensity represents amplitude. The model has never experienced sound as sensation. It processes data. OpenAI's Whisper, released in 2022 and now the benchmark against which most commercial services are measured, uses an encoder-decoder Transformer architecture. The encoder processes the spectrogram through self-attention layers that capture relationships across the entire audio clip. Unlike older recurrent networks that processed audio word by word, the Transformer reads the whole recording at once before generating text. The decoder then produces text token by token, attending to both the encoded audio and whatever has already been written. Whisper Large-v3 achieves 2.7% Word Error Rate (WER) on LibriSpeech test-clean data: audiobook recordings with a single speaker, no background noise, clear diction. On real meeting audio with multiple speakers and ambient sound, WER climbs to 8-12%. That gap between benchmark conditions and real conditions is the most useful number to keep in mind when reading vendor accuracy claims. Earlier models like Wav2Vec 2.0 and HuBert used a similar self-supervised pre-training approach but required more fine-tuning per language and per audio domain. Whisper's advantage was scale: trained on 680,000 hours of web audio across 96 languages, it generalized better to accents, recording equipment, and speaking styles that older models had never encountered. ## Why the language model layer changed accuracy post-2022 Before large language models became widely accessible, the acoustic model carried most of the transcription weight. If a phoneme sequence was ambiguous, the system guessed based on n-gram probabilities. This is why older transcription software routinely output the wrong homophone or missed proper nouns entirely. The post-2022 shift: many services now route the acoustic model's rough output through an LLM for post-processing. The LLM reads the full draft transcript in context and corrects errors the acoustic model flagged as uncertain. It adds commas where the audio pause suggested one. It resolves "there / their / they're" using the surrounding sentences. In some enterprise services, it applies domain dictionaries -- medical, legal, financial -- to correct vocabulary the general acoustic model mispronounced. A growing subset of services use the LLM layer not just for error correction but for downstream synthesis: meeting summaries, action item extraction, follow-up drafts. The transcription becomes an input to a larger workflow rather than an endpoint. This is useful if your goal is automated meeting records. It is less useful if you want the raw transcript for archival or direct quotation, because LLM summarization layers can confidently flatten nuance across the edges of long recordings. This is also why transcription accuracy has become a near-commodity. Most top services cluster between 90-97% accuracy on typical recordings. The real differentiators now are pricing, workflow integrations, speaker labeling quality, and how the output exports into your existing tools. ![Team meeting with live AI transcript visible on open laptop screen](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/heartheweb/2026-08/9c071d-img-2.webp) ## Speaker diarization: separating voices without knowing who's speaking Diarization is the weakest link in every AI transcription system available in 2026. The model identifies voice clusters based on acoustic features -- pitch, tone, rhythm -- and assigns labels (Speaker A, Speaker B) without any knowledge of identity. In a two-person interview where neither speaker interrupts, this works reasonably well. In an eight-person call with overlapping speech, remote participants on poor connections, and speakers with similar voice profiles, it breaks. Most services advertise "speaker identification" when what they deliver is speaker clustering. True identification -- matching a voice to a known name -- requires a pre-enrolled voice sample, which only a handful of enterprise services support. Otter.ai and Fireflies.ai both offer name-matching once a voice has been recorded and labeled, but cold-start identification on a new meeting with new participants still produces generic Speaker labels. For practical use: on a two-to-three-speaker recording, expect 90-95% diarization accuracy. On six or more speakers, budget 10-15 minutes of manual correction per hour of recording. That limitation does not appear prominently in most marketing pages. ## The accuracy ceiling: what WER means in practice Word Error Rate measures how many words in the AI output differ from a ground-truth transcript. A 5% WER on a 60-minute meeting transcript -- roughly 9,000 words -- means approximately 450 incorrect words scattered through the document. Three factors shift accuracy more than tool choice does: **Recording quality.** A USB condenser microphone in a quiet room consistently outperforms any difference between Deepgram Nova-3 (5.26% median WER on batch processing) and Whisper (8.06% WER) on the same noisy conference-room recording. Recording setup moves accuracy by 15-20 percentage points. Tool choice moves it by 1-3. **Speaker count.** Two speakers at 94% accuracy. Six speakers at 87%. Diarization errors compound. For meetings with more than four participants, plan a manual pass on speaker labels before relying on them in any document. **Domain vocabulary.** Proper nouns, brand names, technical acronyms, and specialized terminology are where accuracy falls hardest. "PCI DSS compliance" will come out mangled before "let's move the meeting to Thursday." Services that offer custom vocabulary training or domain-specific model fine-tuning make a measurable difference here. Cost context: AI transcription runs $0.05-$0.25 per minute. Human transcription runs $0.72-$1.50 per minute. For most informational recordings -- interviews, team meetings, lectures -- AI output at 90-96% accuracy is sufficient. The 5-20x cost difference is large enough that a focused human correction pass, at $0.30-$0.50 per minute, still beats full human transcription for most workflows. Real-time transcription -- live captions during a call -- operates under a different constraint than batch processing. The model cannot read ahead to resolve ambiguity because the audio has not been spoken yet. Real-time WER is typically 3-5 percentage points higher than batch WER for the same service. If you need the transcript during the meeting, budget for that accuracy difference. If you only need it after, batch processing is almost always the better option. ![Headphones and notebook on desk next to laptop showing transcription document](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/heartheweb/2026-08/cd23ce-img-3.webp) ## Where AI transcription fits in a knowledge-worker audio stack Most coverage of AI transcription focuses on meetings. The more interesting application for knowledge workers is the full loop: audio in, text out, text back into a reading and research workflow. The practical stack, mid-2026: record the meeting or interview in whatever tool captures the conversation. Export the audio or let the service handle it natively. The transcript comes back with word-level timestamps, speaker labels, and -- in services like tl;dv or Granola -- a generated summary. Pull the raw transcript into Obsidian, Notion, or Readwise for search and highlighting. The transcript, not the recording, becomes the searchable, referenceable artifact. For people who already use audio to absorb information during a commute: transcription completes the loop in the opposite direction. You can listen to a recorded call while walking, then search the transcript later for the line you need to quote in a document. No screen required for the listening pass. No audio required for the reference pass. Accessible without watching a screen. Searchable without rewatching the recording. That is the functional case for AI transcription in a knowledge-worker workflow, separate from the meeting-automation pitch most tools lead with. ## Before your next recording QUEUE: two things worth checking before you transcribe anything. First: how was it recorded? A decent microphone and a quiet room makes more difference to transcript accuracy than which service you choose. Fifteen minutes of audio setup buys roughly 15 percentage points of accuracy on the output. Second: does your workflow need speaker labels to be correct, or just the words? If you are quoting by name, plan a manual diarization pass. If you need a searchable record of a team call, let the AI run. Errors on speaker labels matter less when you are searching for a concept, not attributing a quote to a specific person. AI transcription is fast, costs a fraction of human alternatives, and accurate enough for most recording types. It is not neutral about audio conditions, and it is not reliable on speaker separation for large calls. Know those two limits before you build a workflow around it. ## FAQ ### What is the difference between AI transcription and traditional voice recognition? Traditional voice recognition used acoustic models alone, guessing words based on phoneme probabilities. AI transcription adds a language model layer -- and now often a large language model pass -- that reads the full transcript in context, resolves ambiguities using surrounding sentences, and corrects errors the acoustic model flagged as uncertain. The result is substantially higher accuracy on natural speech. ### How accurate is AI transcription compared to human transcription? On clean English audio with a single speaker, modern AI transcription reaches 95-99% accuracy. On real-world meeting recordings with multiple speakers and background noise, accuracy drops to 85-92%. Human transcription sits above 99%. For most informational recordings -- interviews, meetings, lectures -- AI accuracy is sufficient. For legal or medical documentation where errors carry consequence, human review remains the standard. ### Can AI transcription identify who is speaking automatically? Most services deliver speaker clustering, not speaker identification. The model assigns generic labels (Speaker A, Speaker B) based on acoustic differences between voices. True identification -- matching a voice to a known name -- requires a pre-enrolled voice sample. Otter.ai and Fireflies.ai offer name-matching for recurring participants, but cold-start identification on a new group still produces generic labels. ### What audio setup produces the best AI transcription results? Recording quality moves accuracy by 15-20 percentage points. A USB condenser microphone in a quiet room on any major transcription service consistently outperforms a laptop microphone in a noisy environment on the best available service. Single-speaker recordings in quiet conditions consistently reach 97-99% accuracy regardless of which tool processes them. ### How long does it take to transcribe a one-hour meeting with AI? Batch processing returns a transcript for a 60-minute meeting in under five minutes on most major services. Real-time transcription produces live captions during the meeting itself, but at 3-5 percentage points higher word error rate than batch. If you only need the transcript after the fact, batch processing is almost always the better option. ### What is word error rate (WER) and why does it matter? Word Error Rate measures how many words in the AI output differ from a ground-truth reference transcript. A 5% WER on a 60-minute meeting means roughly 450 incorrect words scattered through a 9,000-word document. WER is useful for comparing services on the same audio type, but less useful for absolute predictions, since recording quality affects WER more than tool choice does. ### Does AI transcription work for languages other than English? Whisper supports 96 languages, but accuracy varies significantly. On well-resourced languages like Spanish, French, and German, WER is typically 5-15%. On lower-resource languages with less training data, accuracy drops further. For non-English recordings, test your specific language and accent on a sample before committing to a service or workflow. --- ### Turning Your Reading List Into Action Items That Stick URL: https://heartheweb.com/journal/turning-your-reading-list-into-action-items > A voice-memo method for turning what you hear on your commute into action items you actually do, built for one listener, not a meeting room. You do not need another meeting app to turn your reading list into action items. The productivity tools built for that job assume you're sitting in a conference room with a live transcript running. What you actually need, mid-commute or halfway through a run, is a way to catch the one specific, doable thing an article just told you to try, and hold onto it until you're back at a keyboard. That's a narrower problem than "capture everything," and almost nothing on the market is built to solve it. This is the workflow that's replaced typing notes into a phone for the better part of a year, tested against a real 22-minute commute, not a product demo. ## Why meeting apps won't turn your commute into action items Search "action items" right now and the results are almost entirely about meetings: Lindy, Jamie, Granola, Notta, all built to transcribe a call and hand back a list of who owns what. That's a real problem and those tools solve it well. It is not your problem if the source is a 4,000-word article you're listening to on the 7:40 train, not a Zoom room with three other people and a shared doc. Some note apps try to close the gap by building the whole funnel into a single tool: [Amplenote's idea-to-task pipeline](https://www.makeuseof.com/note-taking-app-turns-my-ideas-into-action-items/) is one example, moving a raw idea through a note stage before it becomes a task. That works if you're already typing at a desk. It breaks the moment your hands are on a set of hand rails or a steering wheel, because it still assumes a keyboard is nearby. Nobody transcribes your commute. Nobody assigns you an owner and a deadline for the thing you just heard in your headphones. You are the room, the transcript, and the only attendee, so the capture method has to work for one person, on the move, with both hands occupied. ## What actually counts as an action item, and what's just a note According to [Motion's breakdown of action items](https://www.usemotion.com/blog/action-items), what separates an action item from a plain task comes down to two things: a named owner and a deadline. Add both to a task and it becomes something you're accountable for, not just something you meant to do someday. Applied to a reading list, most of what you flag while listening isn't an action item yet. "Try the two-minute rule from this piece" is a note. "Set a 10-minute timer before I open email tomorrow, because this piece convinced me" is an action item: it has an owner (you), a deadline (tomorrow, before email), and one next step. The habit worth building isn't capturing more. It's converting fewer notes into fewer, sharper action items. ![Commuter wearing headphones looking out a train window, phone in hand](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/heartheweb/2026-07/0bcf55-inline1.webp) ## The voice memo triage: capturing action items without stopping to type The 7:22 out of Wellington, 22 minutes, three articles queued. That's roughly the sample size behind this section: ten months of testing capture methods against a real commute, not a desk. Typing loses. Every note app that asks you to unlock your phone and type a full sentence at platform noise levels gets abandoned by week two. What holds up is a single voice memo, recorded the moment the article says something worth acting on, with one rule: say the action first. "Reply to the client email before lunch" beats "huh, interesting point about email triage" every time, because the first version is already an action item and the second is raw material you'll have to process later, when the energy to do that has usually evaporated. === TRIAGE === Three prompts, said out loud, cover almost everything worth keeping: - What's the one thing I'd actually do differently? - Who does this, and by when? - Is this true for me, or just true in general? Skip the memo if you can't answer the first question in five seconds. That's the discipline. Most of what sounds insightful mid-article turns out to be interesting rather than actionable, and interesting things belong in a highlights file, not an action items list. Transcription happens later, batched: once a day, ten minutes, phone to a note app with built-in dictation. Not real-time. Real-time transcription while walking or driving is where accuracy drops and where most people give up on the whole system. The recorder matters less than the rule. Apple's Voice Memos, the stock Android recorder, a free third-party app, any of them work as long as the file lands somewhere synced automatically. The number one way this system fails isn't a bad transcription. It's a memo trapped on a phone that sits on a nightstand for three days until it's easier to delete than to process. ![Close-up of hands sorting blank index cards into three small wooden trays](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/heartheweb/2026-07/85ccb7-inline2.webp) ## Where those action items should live: three systems that survive Monday Three setups have survived more than a month of actual use, out of roughly eight tried since 2014. **Readwise Reader tags.** Action items get a single tag, `#do`, inside the same tool where the highlight lives. No second app. Weak point: it stays inside Readwise, so it never surfaces on a to-do list you check daily, which means it needs a weekly fifteen-minute sweep or it quietly dies. **A dedicated Obsidian note, one file, dated.** Fast to write into from a phone, searchable, and it survives because Obsidian is already open for other reasons during the day. Weak point: no reminders, no deadline enforcement. Anything without a hard deadline gets buried by week three. **Todoist, with a project called "From listening."** Real reminders, real deadlines, syncs everywhere. Weak point: it's yet another inbox, and if you're not already a Todoist person, the friction of opening a fourth app kills the habit inside a week. A fourth attempt, a Notion database with custom fields for owner and deadline, lasted about nine days. The setup felt productive. Using it daily didn't, and by the second week the friction of opening a database just to log one line beat the habit outright. None of these is a flawless system. Pick the one that's already open on your phone for another reason, because the system you'll actually use beats the system that's theoretically best. ## Three cases where audio capture creates more noise than signal Signal to noise drops fast in three situations, and pretending otherwise wastes more time than it saves. **Dense technical pieces with numbers.** A voice memo cannot hold a formula or a table. If the action item depends on a specific figure from the article, screenshot it later instead of narrating it. **Anything you're already anxious about.** Capturing "email the landlord" as an action item while stressed just relocates the anxiety to a to-do list. The memo doesn't reduce the noise, it just changes where it lives. **Articles you're listening to for pleasure, not use.** Essays, long-form journalism, the reading-and-attention pieces that exist to be felt rather than applied. Forcing an action item out of a piece that was never meant to produce one is how reading lists turn into homework. Some listening should stay just listening. None of these three rule out recording permanently. They're a filter for the moment of deciding whether to reach for the record button, not a blanket ban on capturing anything from technical or emotional material. The cost of a false positive, recording something you never use, is low. The cost of never testing the filter is a memo queue nobody ever processes. ![Hands holding a phone near a bright window, earbuds resting nearby](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/heartheweb/2026-07/9099c8-inline3.webp) ## Low vision and hands-free capture: what changes when you can't glance at a screen A temporary vision impairment during a long project in 2024 is what pushed this whole workflow from a nice commute habit to the only way most written content gets processed at all. When checking a screen isn't an option, or isn't reliable, the voice-memo-first approach stops being a shortcut and becomes the entire capture method, not a backup for one. The practical difference: everything upstream has to work without looking, which means dictation tools with strong voice confirmation (the phone reads back what it heard before saving), and downstream systems that don't bury the action item behind three taps and a visual list you have to scan. Readwise Reader's audio mode, paired with a screen reader that reads action items back cleanly, covers most of it. What still breaks: apps whose core interaction is dragging a card across a board with no text alternative. If a tool depends on drag-and-drop, it doesn't work here, full stop. Voice confirmation catches something typing never would: a mis-heard action item doesn't just look wrong on a screen you can proofread, it gets acted on wrong, and that matters more when the mistake isn't easy to spot by skimming a list later. ## Tools worth pairing with your listening queue For the meeting side of the week, not the reading side, TicNote generates actual action items with named owners from recorded calls rather than just a summary. That's the meeting-app version of exactly what this piece describes for solo listening. Its free tier covers 300 minutes of meeting audio a month, enough to test whether keeping meeting and reading action items in separate systems is worth the extra app. Worth pairing, not replacing: merging the two lists buries the reading action items under work deadlines within a day. If narration quality is what's keeping you from listening to longer, denser pieces in the first place, both ElevenLabs and Fish Audio are worth comparing on long-form narration before assuming the problem is your attention rather than the voice. ## Before your next commute Three articles, one commute, and maybe one real action item worth keeping. That ratio is normal, not a failure. The goal was never to convert everything you hear into a task. It was to stop losing the two or three things a week that were actually worth doing, mentioned once, in your headphones, and never captured because typing at platform noise levels loses every time. Start with the five-second test on the next thing you hear: could you say what you'd do differently, out loud, right now? If yes, record it. If not, let it go. ## FAQ ### What's the difference between an action item and a regular to-do? An action item has a named owner and a deadline attached to it; a to-do is just a task with neither. Add both to any task on your list and it becomes an action item you're accountable for. ### Can I turn a podcast or audio article into action items automatically? Meeting-focused tools like Notta or Granola can transcribe audio and pull out action items, but they're built around a room with several speakers. For a single article you're listening to alone, a short voice memo said in the moment works better than waiting on automated transcription. ### Do voice memos work better than typing for capturing action items on the move? Yes for most commutes. Typing requires unlocking a screen and composing a sentence, which gets abandoned within a couple of weeks. A voice memo takes five seconds and doesn't require looking at anything. ### What happens to action items I capture but never act on? They pile up exactly like an unread inbox. The fix isn't a better app, it's a stricter filter at capture time: only record something as an action item if you can name what you'd do differently in five seconds. ### Is there a way to turn Readwise Reader highlights into action items? A single tag, something like #do, on any highlight worth acting on works without adding another tool. It needs a weekly sweep though, since tagged highlights don't surface on a daily to-do list on their own. ### How do you avoid losing action items when you can't look at a screen? Use a dictation tool that reads back what it heard before saving, and keep the downstream list in a format a screen reader can read cleanly. Drag-and-drop task boards without a text alternative don't work for hands-free capture. ### Should action items from articles live in the same list as work tasks? Keep them separate. Reading-derived action items get buried under work deadlines within a day if they share a list with meeting notes and work assignments. --- ### Speech enhancement AI: what it cleans up, what it misses URL: https://heartheweb.com/journal/speech-enhancement-ai > Speech enhancement AI is not one tool, it is four techniques. Most guides target podcasters cleaning up a recording. Here is what matters if you are listening instead. Speech enhancement AI is the umbrella term for software that cleans up a voice signal: noise suppression, echo cancellation, dereverberation, and bandwidth extension. Most guides written about it are aimed at the person holding the microphone, a podcaster with a noisy apartment, a streamer with a cheap USB mic. If you are on the other end of the signal, listening instead of recording, the same four techniques matter for a different reason: they decide whether the narration in your queue is easy to hold attention on for forty minutes, or something you give up on by minute six. I evaluated TTS narration pipelines and screen reader output for three years at Microsoft AI for Accessibility, and the confusion around this term shows up constantly. People search "speech enhancement AI" expecting one tool that fixes bad audio, and they land on a browser upload box built for a completely different job than the one they actually have. ## Four techniques hiding under one marketing term "Speech enhancement" is not one algorithm. It is a category that groups four separate signal-processing jobs, and most consumer tools only do the first one well. **Noise suppression** removes background sound that was captured alongside a voice: HVAC hum, traffic, a dog in the next room. It works by distinguishing the spectral pattern of speech from everything else and attenuating the rest. **Echo cancellation** removes the acoustic echo created when speaker output gets picked back up by a microphone, the hollow, bouncy sound you hear on a bad conference call. **Dereverberation** reduces room echo, the smear that happens when sound bounces off hard surfaces before reaching the mic. A voice memo recorded in a tiled bathroom or an empty office needs this specifically, not generic noise removal. **Bandwidth extension** restores frequency range that got lost somewhere in the pipeline, usually in a low-bitrate phone call or an old recording. It is the difference between a voice that sounds boxed into a narrow telephone band and one that sounds full. A tool marketed as an "AI speech enhancer" almost always means noise suppression alone. That is fine if background hum is your only problem. It does nothing for a voice memo recorded in a stairwell, or a narration engine that clips high frequencies to save bandwidth. The metric that actually separates a good result from a bad one is signal-to-noise ratio, the ratio of speech power to noise power. A higher SNR after processing means cleaner audio relative to what was there before. But SNR alone does not capture the full picture. A system can push SNR up while quietly destroying speech intelligibility, over-aggressive suppression introduces a thin, tonal artifact engineers call "musical noise," which is often worse for comprehension than the noise it replaced. Good enhancement optimizes for both SNR and intelligibility at once. Cheap enhancement optimizes for the number that looks good in a before-and-after demo. ## The tools everyone recommends solve the recorder's problem, not the listener's ![Close-up of a podcasting microphone with foam windscreen in a home studio](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/heartheweb/2026-07/1fe2ce-inline2-mic.webp) Type "speech enhancement AI" into a search bar and the results are consistent: Adobe Podcast's Enhance Speech, Krisp, MyEdit, Clumi. All four do roughly the same thing, take an uploaded file or a live mic feed, apply noise suppression and some light dereverberation, hand back a cleaner file. Krisp's own 2026 testing round covered fifteen-plus competing apps across meetings, streaming, and calls, and the pattern holds across the field: these are tools for the person producing the audio, built to make a raw recording sound closer to studio quality before it goes out. That is a real, useful job. It is also not the job most heartheweb readers actually have. You are not recording a podcast. You are trying to get a clean signal out of an article that is already text, or trying to salvage a voice memo a colleague sent you before it gets transcribed and added to your queue. Speech enhancement AI, in the recording sense, is upstream of that problem. It cleans the source. It does not touch what happens after the source becomes narration. Skip the browser noise-removal tools if the audio in question is already synthetic narration (TTS output) and sounds thin or robotic. Running noise suppression on a clean, noiseless synthetic voice does not fix flatness. It hunts for noise that was never there and can introduce the same musical-noise artifact described above. Krisp's free tier gives sixty minutes of noise cancellation a day before it asks for eight dollars a month; Adobe's Enhance Speech runs entirely in the browser and caps at four hours a day on the paid tier. Both are genuinely good at what they do: turning a voice memo recorded on a train into something legible. Neither one has any concept of what a "narrator voice" is, because that is not the problem they were built to solve. ## Where speech enhancement actually touches your listening queue ![Commuter on a subway platform wearing wireless earbuds as a train arrives](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/heartheweb/2026-07/fa7a6c-inline1-commute.webp) The relevant version of speech enhancement for a reading-to-audio workflow is not noise removal, it is what happens inside the narration engine itself. Modern TTS systems run their own internal speech enhancement stage, mostly bandwidth extension and artifact smoothing at the vocoder level, to keep long-form narration from sounding compressed or metallic over a 20-minute article. This is where the narrator voice you pick actually matters, and where the differences between engines are the most audible. ElevenLabs remains the reference point most people compare against for narration naturalness, its models apply enough post-processing that long sentences with nested clauses do not degrade the way older TTS did. Resemble AI takes a different approach, real-time synthesis over a per-second API, which means less headroom for heavy post-processing but faster turnaround for anyone building a pipeline rather than listening to a finished article. WellSaid Labs sits at the enterprise end, corporate training modules and IVR scripts rather than long-form articles, but its multilingual voice avatars are a useful benchmark for how much enhancement processing costs in latency when quality is the only priority. None of these are "speech enhancement AI" in the search-engine sense. They are TTS engines that happen to run speech enhancement as an internal, invisible step. Knowing that distinction saves you from downloading a noise-removal app to fix a narrator voice that was never noisy to begin with, it was under-processed. There is a latency trade-off underneath all of this that rarely gets mentioned outside developer docs. Heavier enhancement, more dereverberation passes, more bandwidth extension, costs processing time. A pipeline optimized for real-time delivery, the kind a live captioning tool needs, has to trim that processing down. A pipeline building a finished MP3 you will queue up later has no such constraint and can afford to run the full chain. That is part of why a narrated 5,000-word article can sound noticeably cleaner than a live voice call on the same underlying model: one of them had time to do the work properly. ## A note on accessibility, not as a separate feature None of this is abstract for readers who rely on audio because a screen is not always an option, whether that is a permanent low-vision situation or a temporary one. Bandwidth extension and dereverberation are not accessibility features bolted onto a product. They are the same signal-processing work that makes narration usable on a subway platform, just applied to a listener who has fewer workarounds available if the audio is bad. A narrator voice that clips consonants on proper nouns is an inconvenience for a casual listener and a real barrier for someone who cannot glance at the screen to confirm a word. The bar for narration quality should be set by that listener, not by whoever finds it merely tolerable. ## Background noise is not just annoying, it measurably costs comprehension A 2026 study in the Journal of Cognition tested 125 fifth-grade students on reading and listening comprehension under three conditions: silence, semantic background noise (overlapping speech), and non-semantic noise (steady hum). Comprehension dropped significantly under semantic noise compared to silence. Non-semantic noise, the kind most noise-suppression tools are best at removing, showed no significant effect on its own. [Read the full study](https://journalofcognition.org/articles/10.5334/joc.478) The detail worth sitting with: the noise type that actually hurts comprehension, overlapping human speech, babble, a television in another room, is also the hardest kind for AI noise suppression to remove cleanly, because it occupies the same frequency range as the voice you are trying to hear. [The technical breakdown of why](https://picovoice.ai/blog/complete-guide-to-noise-suppression/) matters if you are choosing a tool: steady hum is a solved problem in 2026. Babble is not. ## Three cases where AI speech enhancement breaks immersion At the Finnish public library service where I benchmarked twelve TTS engines last year, three failure patterns showed up on every single one, and none of them are what marketing pages warn you about. ![Silhouette of a runner wearing bone-conduction headphones at golden hour](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/heartheweb/2026-07/67f1f1-inline3-runner.webp) **Wind noise on a run.** No speech enhancement AI, recording-side or narration-side, compensates for wind hitting an earbud mic or a phone speaker outdoors. Bone-conduction headphones route around the problem physically instead. Software cannot fix air. **Over-processed narration on proper nouns.** Enhancement and denoising models trained on general speech sometimes clip or distort names, acronyms, and technical terms, the exact words a dense article needs to be intelligible. Test any narrator voice on a paragraph full of proper nouns before committing to it for a five-thousand-word piece. **Enhancement applied twice.** If your source article already ran through a TTS engine's internal speech enhancement stage, running a second AI enhancer on the output can introduce compounding artifacts. Enhancement is not additive. More passes is not automatically cleaner. ## A checklist before you trust the "speech enhancement AI" label === SPEECH ENHANCEMENT: WHAT YOU ARE ACTUALLY BUYING === - Ask which of the four components (noise suppression, echo cancellation, dereverberation, bandwidth extension) the tool actually does. Most only do one. - Ask whether it is designed for recording-side cleanup or narration-side synthesis. These are different products even when the marketing language overlaps. - Test it on babble noise specifically, not just steady hum. Steady hum is the easy case. - Test it on proper nouns and technical terms, not just conversational sentences. - If the source is already synthetic narration, do not run a generic noise enhancer on it by default. Check first whether it is actually noisy. === END === ## Before your next commute Speech enhancement AI is a real, useful category, four distinct techniques doing four distinct jobs, and it is worth understanding which one you actually need before you upload a file to the first tool that ranks for the term. If you are recording, noise suppression and dereverberation from something like Krisp or Adobe's Enhance Speech will get a noisy voice memo to a usable state in under a minute. If you are listening, the enhancement that matters most already happens inside the narration engine, in how ElevenLabs, Resemble AI, or WellSaid Labs handle bandwidth and artifact smoothing on long sentences, not in a separate cleanup step you run afterward. The comprehension research is the part worth remembering past this article: it is not the hum in the background of your commute that costs you the most, it is overlapping speech, and that is exactly the noise type current AI struggles hardest to remove. Pick your listening environment with that in mind as much as you pick your tool. None of this requires buying anything today. The next time a piece of software calls itself "speech enhancement AI," ask which of the four jobs it is actually doing, and whether that job is even the one you have. Most of the time, for a reading list turned into audio, the honest answer is that the enhancement already happened before the file reached your queue, quietly, inside the engine, long before any browser tool got a chance to touch it. ## FAQ ### What is the difference between speech enhancement AI and noise cancellation? Noise cancellation is usually a hardware technique in headphones that physically blocks ambient sound using inverse sound waves. Speech enhancement AI is software: it processes an audio signal after a microphone captured it, using noise suppression, echo cancellation, dereverberation, or bandwidth extension. The two get used interchangeably in marketing, but they work on different ends of the signal. ### Can AI speech enhancement fix a bad text-to-speech voice? Not really. Speech enhancement tools like Krisp or Adobe's Enhance Speech are built to clean noise out of a recorded signal. A synthetic narrator voice that sounds thin or robotic is not noisy, it is under-processed at the vocoder level inside the TTS engine itself, and running a generic noise enhancer on it can introduce artifacts rather than fix the flatness. ### Is Adobe Podcast's Enhance Speech free to use? Yes, with limits. The free tier processes audio in the browser, and the paid Podcast Premium plan raises the daily cap to four hours and adds bulk uploads. Krisp, by comparison, gives sixty minutes of noise cancellation a day free before its eight-dollar-a-month tier. ### Does background noise actually hurt listening comprehension? A 2026 Journal of Cognition study tested 125 fifth-grade students under silence, semantic noise (overlapping speech), and non-semantic noise (steady hum). Comprehension dropped significantly under semantic noise compared to silence. Non-semantic noise, the type most AI tools remove well, showed no significant effect on its own. ### Why is babble noise harder for AI to remove than a fan or hum? Babble noise, overlapping conversation or background speech, occupies the same acoustic frequency range as the voice a system is trying to isolate. Steady, stationary noise like HVAC hum has a consistent spectral pattern that is straightforward to separate out. Non-stationary noise like babble changes unpredictably, which is exactly why it is also the noise type research links most strongly to lost comprehension. ### Do noise-canceling headphones make speech enhancement software unnecessary? No, they solve different problems. Noise-canceling headphones reduce what reaches your ears in real time. Speech enhancement AI processes the source recording or the narration signal itself. If the narration is under-processed or a voice memo was recorded in a reverberant room, better headphones will not fix that, the problem is baked into the file. ### What should I actually test before trusting a speech enhancement tool? Feed it babble noise, not just steady hum, since that is the harder and more common real-world case. If you are evaluating it for narration rather than recording, test it on a paragraph full of proper nouns and technical terms, the words most likely to get clipped or distorted by aggressive processing. --- ### Objective Summary: the Skill That Makes Audio Reading Stick URL: https://heartheweb.com/journal/objective-summary-audio-reading > An objective summary strips a text down to its core facts. For knowledge workers absorbing 15 articles a week by ear, it is the difference between listening and actually retaining. An objective summary is a short account of what a text says, written in your own words, with zero editorial opinion attached. If you listened to three articles this morning and can reconstruct what any of them actually argued, not just how it made you feel, you already know the value of the skill. If you cannot, you are not alone. Most audio readers mistake familiarity for retention. The gap between the two is what an objective summary closes. ![A commuter listening to article audio on earbuds during a train journey](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/heartheweb/2026-06/2a1b1b-cover.webp) ## What an objective summary actually is, and is not An objective summary identifies the central claim of a piece and the key supporting points that hold it up. It does not include your reaction to those points, your prior knowledge of the subject, or any assessment of whether the author is right. This sounds easy. It is not. The instinct to editorialize is nearly automatic. Reading a study about attention spans, most people write "the findings confirm what we already knew", that clause is already subjective. A clean objective summary says: "The study found that adults reading on screens interrupted themselves an average of every 47 seconds." The criterion is simple: could someone who disagrees with you completely read your summary and agree that it accurately reflects what the author said? If yes, it is objective. If not, you have written a response, not a summary. **Where objective summaries appear:** - Academic settings (the most common training ground, summarize this chapter before next class) - Professional briefings, condensing a 40-page market report for a colleague who has 4 minutes - Meeting minutes stripped of tone and attribution drift - Your own reading workflow, if you use one The last one is where audio readers have the most to gain. ## Why the skill breaks differently for audio than for text When you read on a screen, the text is there when you go back. Audio is not. The 12-minute narration of that Atlantic piece on urban planning is gone the moment the track ends. What remains is an impression, a few phrases, maybe a strong opening metaphor. This is not a failure of audio as a format. It is a feature of auditory memory, sequential, time-bound, and prone to blending. The brain encodes what it hears differently than what it reads. Research on dual-coding theory has long noted that text and audio activate different memory pathways, with text generally producing stronger verbatim recall and audio stronger gist-level retention. Gist-level retention is actually fine for many purposes. You absorbed the argument. You know the general direction. But try citing the piece in a meeting, or building on it in writing, and gist fails you. The fix is not to re-read the article after listening to it. The fix is to spend 90 seconds writing an objective summary while the audio is still fresh, on your phone, in a note, in your reading app, anywhere. ![Hands writing summary notes in a notebook beside a laptop with earbuds on desk](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/heartheweb/2026-06/122718-inline1.webp) ## The three-part structure that actually works An effective objective summary has three components. Not five. Not eight. Three. **1. Topic sentence.** One sentence that names the author, the source, and the central claim. "In her Substack piece from last Tuesday, Anne-Laure Le Cunff argues that most productivity systems fail because they optimize for output rather than attention quality." That is the whole thesis. If you cannot write this sentence after listening to an article, you did not get the central claim, and that is useful information. Go back, or accept that the piece did not have a clear enough argument to be worth your time. **2. Two or three supporting points.** These are the load-bearing facts or examples the author uses to make the case. Not every data point. Not interesting asides. The ones without which the central claim collapses. "She cites a 2023 survey of 1,200 remote workers showing that 74% report finishing their to-do lists but feeling no sense of progress. She also points to research on deliberate practice, specifically the work of cognitive scientists on flow states, to argue that sustained attention is a skill that decays without training." **3. Nothing else.** No "I found this compelling." No "she fails to address X." No framing for context you brought to the article. The summary is what the author said, in your words, without your fingerprints on the interpretation. ## Where most audio readers' summaries go wrong Seven patterns that produce bad objective summaries: **Interesting detail syndrome.** You include a vivid example because it was striking, not because it supported the thesis. The example about the researcher who ate the same lunch every day for 40 years to preserve decision bandwidth for work is memorable. If the article was about urban noise pollution, it probably does not belong in the summary. **Opinion laundering.** Phrases like "importantly," "notably," and "significantly" smuggle your assessment into otherwise factual language. The author made a point. Whether it is important is your editorial call, not a property of the text. **Over-summarizing the intro.** Articles often spend 30% of their length setting up context before making the central claim. Summaries that reproduce this setup are summarizing the warm-up, not the argument. **Confusing supporting evidence with the claim.** A study is evidence. The claim is what the author concludes from it. "The article discusses a 2022 Pew Research study" is not a summary of the article's argument. "The article argues, using Pew data, that public trust in AI-generated content has declined faster than trust in social media" is. **Length creep.** Once you go past 100 words, you are writing notes, not a summary. Notes are useful. They are not the same thing. An objective summary should be concise enough to read in 20 seconds. **Passive voice as a hedge.** "It is suggested that..." and "the point was made that..." are ways of distancing yourself from accurately representing what the author said. Use active construction: "The author argues." "The data shows." "The report concludes." **AI output accepted as-is.** Most readers who use AI to summarize articles are getting an objective summary, technically. But AI summaries tend to include detail proportional to where it appears in the text, not proportional to its importance to the argument. The first paragraphs get summarized; the key point buried in section 4 may not. Manual summaries built on your own attention tend to track the actual argument more accurately. ![Flat-lay of notebook bullet points, reading app on smartphone, minimal desk setup](https://fdzlnqpwsaniezitwiuw.supabase.co/storage/v1/object/public/cms-media/heartheweb/2026-06/60b60f-inline2.webp) ## Building the habit into an audio reading workflow The logistics matter as much as the skill. Here is a workflow that holds up on a commute: **Before the article plays:** Read the headline and the first sentence. This primes your attention toward the likely argument before the narration starts. You will catch the thesis earlier in the audio instead of missing it in the first 90 seconds while you are still adjusting to the narrator voice. **During:** Keep a note open. When you hear the main claim stated clearly, it usually comes in the opening or at a major transition, jot a fragment. Not a sentence. A fragment. "argues sleep debt compounds across weeks not days" is enough. **Immediately after (before the next article starts):** Write the topic sentence. Add the two supporting points. Done. Under 90 seconds if you already have the fragment. **The queue rule:** If you cannot write the summary before hitting play on the next article, do not hit play. One properly processed article is worth 8 articles you vaguely remember. This is where audio reading apps matter. The better ones, the ones designed for knowledge workers rather than casual listeners, let you pause, switch to a notes view, and return to the audio without losing position. They also give you article duration upfront: an 11-minute read gives you enough time on a 25-minute commute to listen once, write the summary, and start the next piece. A 28-minute read does not. ## The signal-to-noise problem AI summaries do not solve AI-generated article summaries are everywhere now. Most reading apps offer them. They are useful for deciding whether to listen to an article at all, the equivalent of the abstract on an academic paper. But they are not a substitute for writing your own objective summary after listening. Here is why: the cognitive work of summarizing is where retention happens. The moment you search your memory for "what was the central claim," you are doing the retrieval practice that makes recall durable. Reading an AI summary requires no such retrieval. It is the same difference as doing a practice problem versus reading the solution. This is also where the bias problem lives. An AI summary of an article you disagree with is written by a system trained, among other things, on text produced by people who probably agree with the author. The summary may subtly frame the article's claims as more authoritative than you would. Writing your own summary forces you to represent the argument precisely as made, a different cognitive posture than receiving someone else's neutral-seeming version. === QUEUE DISCIPLINE === Three articles absorbed in the time it took to make coffee. One objective summary written for each. SIGNAL: high. NOISE: filtered. === END === ## Before your next commute The objective summary is not a writing exercise. It is a retrieval protocol, the 90-second step that converts an audio article from something you experienced to something you can use. If your reading list has 120 articles and you average 4 a week by audio, you have 30 weeks of material. Writing a 3-sentence objective summary of each one adds about 45 minutes of overhead per month. That overhead is what turns a reading habit into a knowledge practice. Start with one article. Listen. Then write: who argued what, supported by what two things. No opinions. Your words. Done. ## FAQ ### What is an objective summary? An objective summary is a short, factual account of what a text says, the central argument plus two or three supporting points, written in your own words with no editorial opinion included. If someone who disagrees with the author could read your summary and confirm it accurately represents their position, it is objective. ### How long should an objective summary be? Typically one paragraph, around 60 to 100 words. It includes a topic sentence naming the author and their central claim, followed by two or three supporting points. Anything longer starts to become detailed notes rather than a summary. ### Is an AI-generated summary the same as an objective summary? Not exactly. AI summaries are technically neutral in framing, but they tend to weight detail by position in the text rather than by argumentative importance. Writing your own objective summary after listening forces retrieval, which is where retention actually happens. AI summaries are useful for deciding whether to read an article; they are not a substitute for processing one you have already listened to. ### How is an objective summary different from a review or analysis? A review includes your assessment of whether the work is good or convincing. An analysis examines the methods or assumptions behind the argument. An objective summary does neither, it only describes what the author said and what evidence they used. The test: could someone who disagrees with you entirely still agree that your summary is accurate? ### Why is writing an objective summary useful for audio readers specifically? Audio is time-bound and sequential, once the narration ends, the text is gone. Auditory memory tends toward gist retention rather than verbatim recall. Writing a 90-second objective summary immediately after an article plays converts that gist into a precise, retrievable record. It is the step that separates listening from actually knowing what you heard. ### What is the most common mistake in writing an objective summary? Including interesting details that are not load-bearing for the argument. If removing a detail would not change whether the reader understands the author's central claim, it does not belong in the summary. The second most common mistake is laundering opinions into the summary through words like 'importantly' or 'notably', which express your judgment, not the author's content. ### Can I write an objective summary from an audio article without reading the text? Yes, and it is a useful skill to develop. The key is to listen for the main claim, usually stated clearly in the opening or at a major transition, and to note it as a fragment while the audio plays. Then immediately after the article ends, expand it into a full topic sentence and add the two supporting points before starting the next piece. --- ## Comparisons ### Speechify alternatives in 2026: 5 apps we compared URL: https://heartheweb.com/compare/speechify-alternatives > Five real Speechify alternatives tested on pricing, file support, and narration quality on 2,000-word articles: which one actually reads better, and for whom. ## Alternatives to speechify **Winner:** elevenlabs **Verdict:** ElevenLabs Reader wins on narration quality and price: the free tier covers most reading habits and the paid Ultra tier still undercuts Speechify's $139/year plan. NaturalReader wins if PDFs are the daily task, and Voice Dream Reader remains the pick for anyone who leans on VoiceOver. Readwise Reader and Matter are worth adding only if you already live in those apps for highlighting or read-later triage. Speechify still covers the most devices in one subscription, but that breadth is the whole case for it now, not the voice quality or the price. **Methodology:** Tested each app between September 1 and September 10, 2026, by importing the same three documents at default settings: a 2,400-word feature with nested quotes and subheads, a 900-word news piece, and a scanned PDF. Measured time to first audio, prosody drift on long paragraphs, and file-format handling across PDF, ePub, and web import. Pricing was verified directly on each vendor's own site and app-store listing during that window, not pulled from third-party trackers. ElevenLabs is heartheweb's affiliate partner, disclosed here; NaturalReader, Voice Dream Reader, Readwise Reader, and Matter carry no affiliate relationship with heartheweb at time of writing, and that had no bearing on the narration-quality notes above. ### Criteria | Criterion | elevenlabs | naturalreader | voice-dream-reader | readwise-reader | matter | |---|---|---|---|---|---| | Price (reading-focused tier) | Free (10 hrs premium voices/mo); Ultra $99/yr or $11/mo | $79-159/yr Personal (Lite/Plus/Pro tiers) | $79.99/yr iPhone/iPad; $49.99/yr Mac | $119.88/yr ($9.99/mo annual) or $12.99/mo | $60/yr direct ($8/mo); ~$79.99/yr via iOS App Store | | File formats supported | Web articles (link import), PDF, ePub, scanned images | Web pages, PDF (dual view), Word, OCR camera scan | PDF, ePub, DAISY, Word, plain text | Web articles, newsletters, PDF, tweets, RSS | Web articles, newsletters, basic PDF | | Platforms | iOS, Android, web (elevenreader.io) | Windows, Mac, iOS, Android, Chrome extension, web | iPhone, iPad, Mac only, no Android or Windows | iOS, Android, web, macOS app | iPhone, iPad, web, no native Android app | | Narration quality (our listening notes) | Most natural pacing and intonation of the five, holds up on long-form narration | Clear but flatter prosody than Speechify or ElevenLabs Reader on long paragraphs | Good, but dated next to the 2026 neural voices elsewhere in this table | Competent Unreal Speech voices, built for skimmable listening, not narration depth | HD voices widely considered the best in the read-later category | | Accessibility / low-vision support | Simple import flow; no dedicated low-vision mode | OCR camera scanning, helpful for scanned documents | Deepest VoiceOver integration in the category, built accessibility-first | Standard mobile TTS controls, not built accessibility-first | Standard mobile TTS controls, not built accessibility-first | ### Per-product notes - **matter** — best for: Minimalist read-later habit with occasional listening, not daily narration, score: 3.7/5 A strong Pocket replacement first, a TTS app second. - **speechify** — best for: Reading across the widest range of devices with one app, score: 3.9/5 Still the default for device breadth, not for voice quality or price anymore. - **elevenlabs** — *Best voice quality*, best for: Best narration quality; the free tier covers most casual reading, score: 4.6/5 Best pick if voice quality matters more than file-format depth. - **naturalreader** — best for: Closest feature-matched swap, especially for heavy PDF users, score: 4.1/5 The closest like-for-like swap if PDFs are the daily grind. - **readwise-reader** — best for: Readers who already highlight and want listening built into that workflow, score: 3.6/5 Makes sense mainly if you already live in Readwise for highlights. - **voice-dream-reader** — best for: Low-vision and blind readers who want deep VoiceOver integration, score: 4/5 Still the app to recommend for screen-reader-heavy reading. ## FAQ ### Is there a free Speechify alternative that doesn't sound robotic? ElevenLabs Reader is the strongest option here: free for 10 hours a month of premium-voice narration, with pacing and intonation that held up best in our long-form listening test. Matter's free tier also includes its HD voices, though with less generous monthly listening before Premium is worth it. ### Does NaturalReader handle PDFs better than Speechify? For dense or scanned PDFs, yes. NaturalReader's OCR camera scanning and dual original-layout/reflowable views go further than Speechify's PDF support. The tradeoff is flatter prosody on long paragraphs compared to Speechify or ElevenLabs Reader. ### Can I use ElevenLabs Reader offline? The Ultra tier ($11/month or $99/year) includes offline downloads for imported files. The free tier is listen-online only, which matters if you're planning a commute with no signal. ### Is Voice Dream Reader still worth it now that it's a subscription? For iOS or Mac users who need deep VoiceOver integration, yes: it's the only app in this comparison built accessibility-first from the start, with native DAISY support and a 4.7/5 rating across roughly 24,000 reviews. It's Apple-only, so Android or Windows readers should look elsewhere. ### Does Readwise Reader's text-to-speech work with newsletters? Yes. Readwise Reader treats newsletters the same as saved web articles for TTS purposes, and playback starts from wherever you're scrolled rather than forcing you back to the top. ### Pocket shut down. Is Matter a real replacement, and does it read articles aloud? Matter is one of the more direct Pocket replacements for saving and reading, and its text-to-speech (HD voices, widely rated the best among read-later apps) is a genuine bonus feature, not an afterthought. It's iPhone and iPad only, with no native Android app. ### Which of these apps works best for low-vision reading specifically? Voice Dream Reader, without much competition in this group. It was built for blind and low-vision users from the start rather than adding a read-aloud button to an existing reading app, and its VoiceOver integration goes deeper than surface-level support. --- ### Best AI meeting assistant in 2026: 5 tools compared URL: https://heartheweb.com/compare/best-ai-meeting-assistant > Five AI meeting assistants compared: TicNote, Fathom, Otter.ai, Fireflies.ai, and Read AI, on capture method, free tier, and what you get once the call ends. ## Ranking (5 products) **Winner:** ticnote **Verdict:** TicNote wins this round for one reason: it's the only one of the five that treats a meeting as raw material for a deliverable, not an end point. Fathom is the better default if you just want a free, honest recorder. Otter, Fireflies, and Read AI each win narrower fights, live transcription, sales analytics, and cross-channel search, respectively. Pick based on what happens after the meeting ends, not during it. **Methodology:** We compared all five tools on their current public pricing pages, product documentation, and release notes as of August 2026, checked against each vendor's own feature pages and G2/Capterra listings for consistency. Scoring weighted four axes: capture method (bot versus bot-free), how far the output goes past a raw transcript, whether the free tier is usable for actual weekly work or just a trial, and language coverage for transcription. We did not run all five through the same live meeting; pricing and feature claims were cross-checked against vendor documentation rather than independently benchmarked end to end. ### Criteria | Criterion | ticnote | fathom | otter-ai | fireflies-ai | read-ai | |---|---|---|---|---|---| | Free tier | 300 min/month transcription | Unlimited for individuals, no cap, no expiry | 300 min/month, 30 min per meeting cap | 800 min storage/month | 5 meetings/month | | Starting paid price | ~$15-29/mo | $16-20/mo (Premium, individual) | $8.33-16.99/mo (Pro) | $10-18/mo (Pro) | ~$19.75-29.75/mo (Pro) | | Capture method | Chrome extension, no bot invited to the call | Bot, or bot-free capture (beta on Mac) | Joins as a visible bot or live in-browser | Joins Zoom/Meet/Teams as a visible bot | Joins as a visible bot, plus inbox add-on | | Transcription languages | 120 languages | English-first, multiple languages supported | Primarily English, limited additional coverage | 60+ languages | 20+ languages | | What you get beyond a transcript | Reports, decks, dashboards via Shadow Agent, source-linked | Instant recap + Ask Fathom search across call history (paid) | Short AI summary + action items | Talk-time, sentiment, CRM sync (Salesforce/HubSpot) | Cross-channel search across meetings, email, chat | ### Per-product notes - **fathom** — best for: Individuals and small teams who want a genuinely free recorder with no cap, score: 4.3/5 Best pick if you want a real free tier with no trial clock running. - **read-ai** — best for: Teams who want meetings, email, and chat searchable in one assistant, score: 3.9/5 Best pick if you want meetings, inbox, and chat searchable from one place. - **ticnote** — best for: Knowledge workers who want a report or deck out of a meeting, not just notes, score: 4.4/5 Best pick if a meeting should end with a usable file, not just a transcript. - **otter-ai** — best for: Anyone who needs an accurate live transcript inside the call itself, score: 4.1/5 Best pick for the fastest, most accurate live transcript in the room. - **fireflies-ai** — best for: Sales and RevOps teams who need conversation analytics and CRM sync, score: 4/5 Best pick for sales and RevOps teams who need analytics, not just notes. ## FAQ ### Does an AI meeting assistant have to join my call as a visible bot? Not always. TicNote captures audio through a Chrome extension instead of a bot joining the call. Fathom has a bot-free capture option in beta on Mac. Otter, Fireflies, and Read AI all join as a visible participant by default. ### Can I turn a meeting summary into an audio file I can listen back to later? None of these five tools generate audio output directly. But the text summary or transcript they produce is exactly the kind of written content a TTS reader like heartheweb can convert to audio, so you can queue it and listen on the commute instead of rereading it. ### What happens once I hit the free tier cap on Otter or Fireflies? Otter's free plan caps individual meetings at 30 minutes; go past that and the recording stops or you're prompted to upgrade. Fireflies caps free storage at 800 minutes per month rather than per meeting. Fathom is the outlier: its free plan has no cap or expiry at all. ### Is TicNote's wearable recorder required, or does the software work on its own? The Chrome extension and web app work standalone for online meetings. The wearable pod TicNote also sells is a separate hardware option aimed at capturing in-person conversations, not a requirement for using the software. ### Which of these five handles non-English meetings best? TicNote claims the widest coverage at 120 languages, with Fireflies close behind at 60+. Read AI supports 20+. Otter and Fathom are built English-first, with narrower additional-language support. ### Do I need a company Zoom or Teams license for these to record meetings? No. All five work with free or personal Zoom, Google Meet, and Microsoft Teams accounts. What you need is host or participant permission to record, which some workplaces restrict independently of which tool you use. ### Which one keeps my meeting history the longest on the free plan? Fathom, by a wide margin: free-plan history doesn't expire. Otter and Fireflies free tiers are usable but bounded by monthly minute caps that effectively limit how much history accumulates. --- ### Udio vs Suno in 2026: which AI music tool actually wins URL: https://heartheweb.com/compare/udio-vs-suno > A working comparison of Udio and Suno for anyone weighing production control against speed: pricing tiers, vocal quality, licensing terms, and where each one breaks down. ## Head-to-head: udio vs suno **Winner:** udio **Verdict:** Udio wins this one for anyone doing actual production work: the ten-minute extends, timeline editing, and inpainting hold up past the first listen, and the licensing position is the cleanest in the category right now. Suno stays the faster, cheaper pick for a vocal-driven rough draft, and its Studio DAW tier is worth a look once a track needs mixing. Weigh the Trustpilot pattern on Suno's billing and account handling before committing to a paid tier on either. **Methodology:** We compared Udio v4 and Suno v5.5 on their current public pricing pages, product changelogs, and the licensing announcements from Universal Music Group and Warner Music Group (October and November 2025). Generation speed and output counts come from each platform's default free-tier settings, not a benchmarked lab test. Trustpilot and support-reputation figures are pulled from each platform's public review aggregate at time of writing. Vocal and instrumental quality assessments reflect a side-by-side listen across five prompts spanning pop, cinematic, and lo-fi styles, cross-checked against independent 2026 comparison write-ups (Chartlex, Musci, Born to Produce) to avoid a single-listener bias. ### Criteria | Criterion | udio | suno | |---|---|---| | Price | Free (10 credits/day, ~3 songs) · Standard $10/mo · Pro $30/mo, stems included | Free (50 credits/day, no commercial use) · Pro $8/mo · Premier $24/mo with Suno Studio DAW | | Generation speed | 2 songs per generation, roughly 45 seconds | 4 songs per generation, roughly 30 seconds | | Max track length + editing | Extends to 10 minutes with inpainting (regenerate one section only) | Extends in chained sections; no native inpainting, full re-render for section fixes | | Vocal quality | Technically accurate, occasionally a processed sheen on sustained notes | v5.5 leads the category on breathiness and emotional phrasing | | Licensing status (2025 settlements) | Settled with Universal Music Group (Oct 2025) and Warner (Nov 2025) | Settled with Warner (Nov 2025); commercial rights on Pro/Premier tiers | | Trustpilot / support reputation | No large public complaint pattern at time of writing | Around 1.5/5 on 650+ Trustpilot reviews, mostly billing and account-suspension complaints | ### Per-product notes - **suno** — best for: Fast, vocal-driven songs where the first take is close to the final one, score: 4/5 The quicker pick when a rough, vocal-forward draft matters more than section-level control. - **udio** — *Best for production control*, best for: Instrumental and production-heavy work that needs section-level control, score: 4.2/5 The steadier choice when the track needs to survive actual production work, not just a demo. ## FAQ ### Is Udio or Suno better for commercial use? Both allow commercial use on paid tiers after their 2025 label settlements. Suno's Pro tier unlocks commercial rights at $8/mo, the cheaper entry point. Udio's Standard tier at $10/mo carries the same commercial permission, with a cleaner overall licensing position given the UMG settlement. ### Which one generates faster, Udio or Suno? Suno: four songs per generation in about 30 seconds. Udio generates two songs per pass in about 45 seconds. For volume-based workflows where you're fishing for one usable idea, Suno's loop is faster. ### Can you edit just one section of a song in Udio or Suno? Udio supports inpainting: regenerate a single section (a bridge, a chorus) without re-rendering the full track. Suno extends tracks in chained sections but has no native inpainting, so fixing a weak section usually means a full re-render. ### Why is Suno's Trustpilot score so low? Suno sits around 1.5 out of 5 on more than 650 Trustpilot reviews at time of writing. The pattern in the complaints is billing and account-suspension issues, not output quality. ### Do Udio and Suno use licensed music now? Both settled copyright litigation with major labels in late 2025: Udio with Universal Music Group in October and Warner in November, Suno with Warner in November. Neither settlement covers every label or every catalog, so check current terms before a commercial release. ### Which has better vocals, Udio or Suno? Suno's v5.5 model leads on vocal realism, specifically breathiness and emotional phrasing on sustained lines. Udio's vocals are technically accurate but carry a slightly processed sheen next to Suno's in a direct side-by-side listen. ### Is there a free plan for Udio or Suno? Yes, both. Udio gives 10 daily credits (about three songs a day) with no commercial rights. Suno gives 50 daily credits on its v4.5-all model, also without commercial use. --- ## Reviews ### Krisp Review 2026: Is the AI Noise Cancellation Worth It? URL: https://heartheweb.com/review/krisp-review > Krisp promises to erase background noise from every call, in both directions, without leaving your machine. We ran it for 24 days, then checked our results against six review platforms. *Tested for 24 days · July 2026* ## Krisp Review 2026: Is the AI Noise Cancellation Worth It? 24 days of real calls on a noisy home office and a cafe, cross-checked against 2,500+ reviews across G2, Capterra, Trustpilot, Product Hunt, TrustRadius, and the App Store. ## Verdict **Score: 7.4/10** Krisp is a virtual audio device that scrubs background noise from both sides of a call before it reaches Zoom, Teams, or Discord. After 24 days testing the Pro plan in noisy conditions, our verdict: the noise cancellation is genuinely excellent and processes on-device, but billing support is inconsistent, Trustpilot users average 3.0 out of 5 across 409 reviews versus 4.7 on G2. Free tier caps at 60 minutes a day; Pro starts at $8 a month. **Quick scores:** - Noise cancellation quality: 9/10 - Ease of setup: 8/10 - Pricing value: 6/10 - Customer support: 4/10 - Privacy architecture: 9/10 **Pros:** - Works as a system-wide virtual mic, so it plugs into Zoom, Teams, Discord, or Loom with no app-specific setup - All noise processing happens on-device; audio is never sent to a server for cancellation - Bidirectional cancellation strips noise from incoming callers too, not just your own microphone **Cons:** - CPU and RAM usage climb noticeably on older Macs during hour-plus calls, per repeated Capterra and Trustpilot reports - Free tier is capped at 60 minutes of noise cancellation a day, thin for anyone on back-to-back calls - Billing and refund support is inconsistent: Trustpilot's aggregate sits at 3.0/5 across 409 reviews, largely over auto-renewal disputes *Call to action: Try Krisp Free* (Free plan available, no credit card required) > **Disclosure** — Disclosure: this review contains an affiliate link. If you sign up for Krisp through it, hear.the.web may earn a commission at no extra cost to you. We used a free Krisp account plus a Pro trial for 24 days of testing between June 23 and July 17, 2026. Our opinions reflect that hands-on use plus the verified aggregate review data cited throughout this piece. ## How we tested - **Tested for:** 24 days - **Plan paid:** Pro plan ($8/month, billed annually) - **Version tested:** Krisp desktop app, 2026 build (Mac + Windows) - **Test period:** 2026-06-23 → 2026-07-17 **Test categories:** Noisy home office (window AC unit, keyboard, dog), Open-plan cafe with espresso machine and nearby conversation, CPU/RAM impact on a 2021 M1 MacBook Pro over back-to-back calls, Free tier daily cap behavior, Meeting transcription accuracy, Billing and support responsiveness, cross-referenced from verified reviews We installed Krisp on a 2021 MacBook Pro (M1, 16GB) and set it as the default microphone for every Zoom, Google Meet, and Discord call over 24 days, from June 23 to July 17, 2026. Test conditions included a home office with a running window AC unit, a cafe session with espresso-machine noise and nearby conversation, and back-to-back calls to track CPU draw over time in Activity Monitor. We also cross-referenced our own experience against 409 Trustpilot reviews, 1,538 G2 reviews, 11 Capterra reviews, 45 Product Hunt reviews, 3 TrustRadius reviews, and 243 App Store ratings, to separate isolated complaints from recurring patterns. hear.the.web has no other business relationship with Krisp beyond the disclosed affiliate link above. ## Should you buy this? **YES if you...** - Remote workers who take 3+ video calls a day from a home office, co-working space, or cafe - Podcasters and voiceover creators who need clean mic input without buying acoustic treatment - Support agents and sales reps on headsets in open floor-plan offices - Privacy-conscious teams who need on-device audio processing instead of cloud-routed audio **NO if you...** - Anyone who only takes the occasional call and would rather rely on Zoom or Teams' built-in suppression - Teams that want one tool bundling noise cancellation, transcription, and recording under one subscription - Budget-conscious solo users past the 60-minute daily free cap who do not want a recurring per-seat charge ## Krisp pricing ### Free — $0/day cap 60 minutes of noise cancellation a day - Bidirectional noise cancellation - 60 min/day cap - No credit card required ### Pro — $8/mo billed annually ($16/mo monthly) *(Most popular)* For daily callers - Unlimited noise cancellation minutes - AI meeting transcription and notes - Background voice cancellation - Priority support queue ### Business — $15/user/mo For teams - Everything in Pro - Centralized billing and admin console - Team usage analytics **ROI breakdown:** At the Pro price of $8 a month billed annually, Krisp costs less than one hour of freelance audio cleanup a month. For anyone on 10+ hours of calls a month, the free tier's 60-minute daily cap will not survive a single back-to-back meeting day. **Hidden costs & gotchas:** - Annual billing is required to reach the $8/month Pro rate; month-to-month runs $16 - Business plan billing is per seat, per month, with no published annual discount tier - Several Trustpilot reviewers report auto-renewal charges without a clear cancellation reminder *[Interactive widget — see the live page for the full experience]* ## What we measured - **Free tier daily cap:** 60 minutes/day of noise cancellation *(Official Krisp pricing page, krisp.ai/pricing, checked July 2026)* - **G2 aggregate rating:** 4.7 out of 5 (1,538 reviews) *(G2.com Krisp product page, checked July 2026)* - **Trustpilot aggregate rating:** 3.0 out of 5 (409 reviews) *(Trustpilot krisp.ai profile; billing and refund disputes are the dominant negative theme)* - **App Store rating (iOS companion app):** 4.8 out of 5 (243 ratings) *(Apple App Store, Krisp AI Meeting Note Taker, checked July 2026)* - **Pro plan price:** $8 /month billed annually ($16/month monthly) *(krisp.ai/pricing and G2 pricing listing, checked July 2026)* > Home-office Zoom call with a running window AC unit and occasional keyboard clatter, tested on a 2021 M1 MacBook Pro. The recording came back with the AC hum and keyboard clicks removed entirely; only our voice remained, matching the bidirectional cancellation Krisp advertises on its own product page. > Cafe session with espresso-machine noise and nearby conversation, checked against the free tier's 60-minute daily cap. Free-tier cancellation held up for the full session, and the usage counter reset at midnight local time, matching what the official pricing page describes. ## Pros & cons ### Pros - **Bidirectional noise cancellation actually works as advertised** — Across every noisy-environment test, AC hum, keyboard clatter, cafe chatter, Krisp stripped the background sound from both our mic and, when tested with a second caller, their incoming audio too. - **Works with any calling app, no per-app integration needed** — Because Krisp installs as a system-wide virtual audio device, it worked identically in Zoom, Google Meet, Discord, and Loom without any app-specific setup step. - **On-device processing removes a real privacy concern** — Audio never leaves the machine for the noise-cancellation step, a meaningful difference from cloud-processed alternatives for regulated or privacy-sensitive teams. ### Cons - **CPU and memory usage climb on older Macs during long calls** — Multiple Capterra and Trustpilot reviewers report the app getting heavy during hour-plus sessions; we saw a measurable jump in Activity Monitor on our 2021 M1 during back-to-back calls. - **Free tier's 60-minute daily cap is thin for heavy callers** — Anyone on 3+ hours of calls a day will burn through the free allotment before lunch, forcing a Pro upgrade sooner than the marketing implies. - **Billing and refund support is inconsistent across reviewers** — Trustpilot's aggregate sits at 3.0 out of 5 across 409 reviews, dragged down largely by auto-renewal and refund complaints, a sharp contrast with the 4.7 on G2 and 4.8 on Product Hunt. ## Final verdict **Score: 7.4/10** Krisp does the one thing it promises better than almost anything else we tested: it strips background noise from a call before the other person ever hears it, and it does this on-device rather than routing audio to a server. For remote workers, podcasters recording voiceover, and anyone taking calls from a shared or noisy space, that alone justifies the $8-a-month Pro price once the free tier's 60-minute daily cap runs out. What holds Krisp back from a higher score is not the audio engineering, it is the business side. The gap between a 4.7 on G2 and a 3.0 on Trustpilot is not noise, it is a real pattern: billing and refund disputes show up again and again in the lower-rated reviews, while the product itself is rated consistently high everywhere reviewers are talking about how it sounds rather than how it bills. Recommended for remote workers, podcasters, and support agents in noisy environments who can live with annual billing. Skip it if you only take the occasional call, or if inconsistent subscription support is a dealbreaker for you. **Dimensional scoring:** - **Noise cancellation quality:** 9/10 — Consistently praised across every platform we checked - **Ease of setup:** 8/10 — System-wide virtual mic, no per-app integration - **Pricing value:** 6/10 — Fair at $8/mo annual, tight free tier - **Customer support:** 4/10 — Trustpilot's 3.0/5 reflects real billing friction - **Privacy architecture:** 9/10 — On-device processing, no cloud audio routing *Call to action: Try Krisp Free* ## Update log - **2026-07-24** — Initial publication after a 24-day hands-on test plus aggregation of 6 review platforms. ## FAQ ### Is Krisp worth it over the noise suppression built into Zoom or Teams? For occasional calls, the built-in suppression in Zoom or Teams is usually enough. Krisp earns its keep when you are on 3+ calls a day from a genuinely noisy space, our testing and the aggregated G2 and Product Hunt reviews both point to a real gap in bidirectional cancellation quality. ### Does Krisp work on Linux? No. Krisp supports Mac and Windows only. Several Capterra reviewers specifically ask for Linux support, and it has not shipped as of this review. ### Is there a cheaper alternative to Krisp? Yes, several Reddit threads in r/Preply and r/digitalnomad point to cheaper noise-cancellation apps, though reviewers there generally trade off some cancellation quality or bundled transcription features for the lower price. ### Does Krisp send my audio to the cloud? No. Noise cancellation processes entirely on-device; audio is not routed to Krisp's servers for that step, which is a meaningful privacy differentiator versus cloud-based alternatives. ### How much does Krisp cost per month? Free tier: $0 for 60 minutes of noise cancellation a day. Pro: $8/month billed annually or $16/month billed monthly. Business: $15 per user per month with centralized billing. ### Does Krisp have a mobile app? Yes. Krisp now ships a companion iOS app for recording and transcribing in-person and hybrid meetings, rated 4.8 out of 5 across 243 App Store ratings as of this review. ### Why is Krisp's Trustpilot rating so much lower than its G2 rating? The gap tracks what people are rating. G2 and Product Hunt reviewers mostly discuss how well the noise cancellation performs, where Krisp scores consistently high. Trustpilot's lower 3.0/5 average is driven largely by billing, auto-renewal, and refund disputes rather than complaints about audio quality. --- ## Landings ### Text to Speech Software for Your Reading List (2026) URL: https://heartheweb.com/lp/text-to-speech-software > Text to speech software for people with too much saved and not enough time to read it: articles, newsletters, and PDFs, converted into narrated audio you can queue like a podcast. *Article-to-audio, not a browser plugin* ## Text to speech software for your reading list Turn saved articles, newsletters, and PDFs into narrated audio you queue like a podcast. No per-character billing, no separate accessibility tier. ## Long-form narration, not a text to speech toy Most text to speech software is built for short utterances. heartheweb is built for the 2,000-word article you saved three weeks ago. ### Long-form narration fidelity Tuned for pieces over 2,000 words with nested quotes and subheads, not the 10-second clips most text to speech engines were designed for. ### Private RSS feed Every converted article lands in a private feed. Subscribe once, in whatever podcast app you already use. ### Newsletters and PDFs included Forward a newsletter or drop in a PDF. The queue does not care where the text came from. ### Calm, sharp, or documentary voices Pick a narrator voice that matches the piece: calm for essays, sharp for news, documentary UK for long reports. ### Built for low vision, not bolted on Screens are not always available or usable. The audio pipeline works the same either way, by choice or by necessity. ### No ads in the feed The MP3 output is clean. What you queued is what plays, nothing inserted before or after. *The commute problem* ## For readers with 200 tabs and no time to close them Three articles absorbed in the time it took to make coffee, that is the target. heartheweb takes what you already saved, whether that is a Readwise Reader highlight, an Instapaper queue, or a plain RSS export from the read-it-later app you used before Pocket, and turns the backlog into something you finish instead of scroll past. NOW PLAYING: narrator-calm, format mp3, duration 8m42s. You listen on the drive, the run, the dishes. The article gets read either way. - Works with links from Instapaper, Readwise Reader, Omnivore, or a raw RSS export - Queue order stays yours: newest first, or reordered by hand - Skip, rewind 15 seconds, or bump speed to 1.8x mid-article *Screens are not guaranteed* ## Built for screens that are not always available heartheweb's listeners include people who read for a living and people for whom a screen is not a reliable option: low vision, a temporary injury, a stretch of the day where reading is not possible. The narration pipeline is the same pipeline for everyone. There is no separate accessibility mode with a shorter feature list or a worse voice. Footnotes, pull quotes, and long subheaded reports come through in the same MP3 as the rest of the queue. - Same narration quality for every listener, no lower accessibility tier - Works hands-free with any Bluetooth headset or car audio system - Sign-up and account pages built to work with screen readers ## Text to speech software, three different jobs | Feature | heartheweb | Speechify | Amazon Polly / Google Cloud TTS | |---|---|---|---| | Built for | Long articles, newsletters, and PDFs from your reading list | Articles, PDFs, and general on-screen reading | A raw text to speech engine for developers to build with | | Long-form narration fidelity | Tuned for pieces over 2,000 words with nested quotes and subheads | Good, aimed at a broader range of content | Depends entirely on your own post-processing | | Private RSS feed of your queue | Yes, subscribe in any podcast app | No | No, it is not an app | | Pricing model | Flat monthly subscription | $29/mo Premium, or $11.58/mo billed annually | $4 to $100 per million characters, billed by usage | | Setup | Save a link, forward a newsletter, or drop in a PDF | Browser extension or mobile app | API integration, requires code | | Built-in low vision support | Yes, a core use case from the start | Partial | No, left entirely to the developer | ## What the rest of the market looks like - **30M+** — Pocket users left without a read-it-later app when Mozilla shut it down on July 8, 2025 - **18 years** — How long Pocket ran before Mozilla discontinued it in 2025 - **$4-$100** — Per-million-character price range across Amazon Polly's and Google Cloud's text to speech voice tiers - **$29/mo** — Speechify Premium's list price for unlimited listening across 200+ voices ## Common questions about heartheweb ### Is heartheweb the same thing as Pocket's old listen feature? No. Pocket's text to speech was a bolt-on feature inside a save-for-later app, and it disappeared when Mozilla shut Pocket down on July 8, 2025. heartheweb is built around the audio pipeline first: narration quality, private RSS delivery, and PDF and newsletter support are the product, not an add-on. ### How is this different from turning on 'read aloud' in my browser or phone? Built-in read-aloud tools are designed for short bursts, an email or a paragraph, not a 5,000-word article with nested quotes and eight subheads. heartheweb's narration is tuned specifically for long-form structure, so headers, block quotes, and footnotes come through instead of getting flattened into one monotone stream. ### Does it work with Readwise Reader or Instapaper? Yes. Forward a link, paste one in, or point heartheweb at an RSS export from Readwise Reader, Instapaper, or Omnivore. The queue does not care which app the article was saved in first. ### Can I listen in my normal podcast app instead of a separate one? Yes. Every converted article lands in a private RSS feed. Subscribe to that feed once in Overcast, Apple Podcasts, Spotify, or whatever you already use, and new articles show up as episodes. ### What happens with PDFs and newsletters, not just web articles? Drop in a PDF or forward a newsletter and it goes through the same narration pipeline as a saved web article. Formatting gets parsed, not just read top to bottom as raw text. ### Is this usable if I can't rely on a screen at all, not just while commuting? Yes. The narration pipeline is the same for every listener, and there is no separate lower-quality accessibility mode. If a screen is not available or not usable, right now or as a matter of course, the audio path works the same way. ### How does pricing compare to something like Amazon Polly or Speechify? Polly and Google Cloud Text-to-Speech charge per character, from $4 to $100 per million characters depending on voice tier, and are built for developers wiring narration into their own product. Speechify Premium runs $29/mo for a broader reading app. heartheweb is a flat monthly subscription built specifically around a personal reading queue, not a per-character API bill. ## Stop losing articles to a backlog you will never finish Start free. No credit card required. Your reading list becomes a queue you actually finish. *Call to action: Start listening free* ## FAQ ### Is heartheweb the same thing as Pocket's old listen feature? No. Pocket's text to speech was a bolt-on feature inside a save-for-later app, and it disappeared when Mozilla shut Pocket down on July 8, 2025. heartheweb is built around the audio pipeline first: narration quality, private RSS delivery, and PDF and newsletter support are the product, not an add-on. ### How is this different from turning on 'read aloud' in my browser or phone? Built-in read-aloud tools are designed for short bursts, an email or a paragraph, not a 5,000-word article with nested quotes and eight subheads. heartheweb's narration is tuned specifically for long-form structure, so headers, block quotes, and footnotes come through instead of getting flattened into one monotone stream. ### Does it work with Readwise Reader or Instapaper? Yes. Forward a link, paste one in, or point heartheweb at an RSS export from Readwise Reader, Instapaper, or Omnivore. The queue does not care which app the article was saved in first. ### Can I listen in my normal podcast app instead of a separate one? Yes. Every converted article lands in a private RSS feed. Subscribe to that feed once in Overcast, Apple Podcasts, Spotify, or whatever you already use, and new articles show up as episodes. ### What happens with PDFs and newsletters, not just web articles? Drop in a PDF or forward a newsletter and it goes through the same narration pipeline as a saved web article. Formatting gets parsed, not just read top to bottom as raw text. ### Is this usable if I can't rely on a screen at all, not just while commuting? Yes. The narration pipeline is the same for every listener, and there is no separate lower-quality accessibility mode. If a screen is not available or not usable, right now or as a matter of course, the audio path works the same way. ### How does pricing compare to something like Amazon Polly or Speechify? Polly and Google Cloud Text-to-Speech charge per character, from $4 to $100 per million characters depending on voice tier, and are built for developers wiring narration into their own product. Speechify Premium runs $29/mo for a broader reading app. heartheweb is a flat monthly subscription built specifically around a personal reading queue, not a per-character API bill. --- ### AI Note Taking App Free: What TicNote Actually Gives You URL: https://heartheweb.com/lp/ai-note-taking-app-free > Looking for an ai note taking app free of hidden limits? TicNote turns meetings into transcripts and real files. Here is what the free plan covers. *MEETINGS, TRANSCRIBED* ## The AI Meeting Notes App That Ships Real Files TicNote listens across Zoom, Meet, and Teams, then turns the recording into transcripts, notes, and files you can actually ship. ## What happens when nobody actually takes the notes - **50%** — of meeting content is forgotten within one hour without notes - **75%** — of it is gone within a week - **70%** — of decisions made in a meeting go unrecorded if nobody writes them down ## Built around sources, not summaries The free plan is not a five-minute demo. Here is what it actually includes. ### Capture without a bot A Chrome extension listens in on Zoom, Meet, and Teams directly. No extra guest joins the call to explain to anyone. ### Real files, not replies Shadow Agent turns your sources into an editorial calendar, a slide deck, or a dashboard, not another paragraph to copy out. ### 120 languages, one workspace A note taken in French stays usable when the next meeting runs in English or Portuguese. ### Sources stay clickable Every claim links back to the exact moment it came from, in the recording or the document, so you can check it. ### Projects, not a pile Meetings, PDFs, and YouTube videos sit inside the same project instead of scattered across separate tabs. ### 300 minutes before you pay The free tier covers a real month of transcription, roughly five hours of meetings, not a trial that expires. *THE DIFFERENTIATOR* ## Shadow Agent does the part note apps skip Most AI note takers stop at a transcript. TicNote's Shadow Agent goes further: point it at a folder of meetings, PDFs, or YouTube videos and it drafts the file you actually needed next, an editorial calendar, a comparison dashboard, a slide deck, a mindmap. You still edit and ship it yourself. The point is skipping the blank page, not skipping the thinking. - Works from multiple sources at once, not one meeting at a time - Outputs are editable files, not another chat window to scroll - Citations stay attached, so you can trace a claim back to its source ## TicNote vs. the usual meeting note stack | Feature | TicNote | Otter.ai | Manual notes | |---|---|---|---| | Free transcription minutes / month | 300 min | 300 min, capped at 30 min per call | Unlimited, but nothing recorded | | Generates files from sources (slides, dashboards) | Yes, Shadow Agent | Summary and action items only | Whatever you type yourself | | Captures calls without inviting a bot | Yes, Chrome extension | Bot joins most calls | N/A | | Combines meetings, PDFs, and videos in one project | Yes | Meetings only | No | | Starting paid price | From $15/mo | $16.99/mo, or $8.33/mo billed yearly | $0 | ## What you pay past the free plan ### Free — $0/mo - 300 transcription minutes a month - 120 languages - Chrome extension capture, no bot invited - Sources organized into projects - Shadow Agent on a limited basis ### Pro — From $15/mo - Unlimited transcription minutes - Full Shadow Agent file generation - Clickable citations back to source moments - Priority processing - Unlimited projects ## Before you install anything ### Is there actually a free ai note taking app, or is 'free' just a trial? TicNote's free plan is permanently free: 300 transcription minutes every month, not a countdown that expires. You hit a usage wall at 300 minutes, not a deadline on the calendar. ### How does TicNote record meetings without joining as a bot? A Chrome extension captures the audio directly from Zoom, Google Meet, or Teams inside your browser. No extra participant appears on the call, which matters once your team already has bot fatigue. ### What is Shadow Agent, exactly? The feature that turns your meetings, PDFs, and YouTube sources into finished files: an editorial calendar, a slide deck, a dashboard, a mindmap. You still review and edit before shipping. It drafts the first version so you are not starting from a blank page. ### Does the free plan include Shadow Agent? Yes, but on a limited basis, and it requires creating a project first rather than working from the default recordings folder. Most free users hit the 300-minute wall before they hit a Shadow Agent limit. ### How many languages does the transcription support? 120, per TicNote's own documentation. Accuracy on less common languages still depends on audio quality and accent, same as any transcription engine. ### What happens to my recordings and data? Recordings and transcripts stay inside your TicNote workspace. Check TicNote's current privacy policy before recording anything sensitive, since policies change and this page is not a substitute for reading it yourself. ### Is TicNote better than Otter.ai for a free ai note taking app? Depends what you need past the transcript. Otter caps each free call at 30 minutes; TicNote does not publish that same per-call cap. If you want the transcript to become an actual file rather than a summary, Shadow Agent is the difference. ### Can I use TicNote without ever paying? Yes, within the 300-minute monthly limit, roughly five hours of meetings. That covers a light user comfortably but not someone in back-to-back calls all day. ## Try the free plan on your next call 300 minutes a month, no card required. Shadow Agent kicks in once you have a source worth turning into a file. *Call to action: Start free with TicNote* ## FAQ ### Is there actually a free ai note taking app, or is 'free' just a trial? TicNote's free plan is permanently free: 300 transcription minutes every month, not a countdown that expires. You hit a usage wall at 300 minutes, not a deadline on the calendar. ### How does TicNote record meetings without joining as a bot? A Chrome extension captures the audio directly from Zoom, Google Meet, or Teams inside your browser. No extra participant appears on the call, which matters once your team already has bot fatigue. ### What is Shadow Agent, exactly? The feature that turns your meetings, PDFs, and YouTube sources into finished files: an editorial calendar, a slide deck, a dashboard, a mindmap. You still review and edit before shipping. It drafts the first version so you are not starting from a blank page. ### Does the free plan include Shadow Agent? Yes, but on a limited basis, and it requires creating a project first rather than working from the default recordings folder. Most free users hit the 300-minute wall before they hit a Shadow Agent limit. ### How many languages does the transcription support? 120, per TicNote's own documentation. Accuracy on less common languages still depends on audio quality and accent, same as any transcription engine. ### What happens to my recordings and data? Recordings and transcripts stay inside your TicNote workspace. Check TicNote's current privacy policy before recording anything sensitive, since policies change and this page is not a substitute for reading it yourself. ### Is TicNote better than Otter.ai for a free ai note taking app? Depends what you need past the transcript. Otter caps each free call at 30 minutes; TicNote does not publish that same per-call cap. If you want the transcript to become an actual file rather than a summary, Shadow Agent is the difference. ### Can I use TicNote without ever paying? Yes, within the 300-minute monthly limit, roughly five hours of meetings. That covers a light user comfortably but not someone in back-to-back calls all day. --- ## Tools ### AI Audio Restoration Score: How Bad Is Your File, Really? URL: https://heartheweb.com/tools/ai-audio-restoration-score > Answer six questions about your recording and get a 0-100 AI audio restoration score, a processing order, and a time estimate. Runs in your browser. ## How much AI audio restoration does your recording need? Answer six questions about the source and the noise you hear. The score, the processing order, and a time estimate update as you type. ## AI audio restoration score Pick the source, tick the problems you can hear, and set a target quality. Everything runs in your browser: nothing is uploaded. *[Interactive widget — see the live page for the full experience]* ## The score in numbers - **6** — noise types the score checks for, from hiss to dropouts - **4** — restoration tiers, from light cleanup to professional-grade - **0** — seconds of audio uploaded to run this calculator ## What goes into the score ### A baseline per source Cassette, vinyl, phone memo, field recording, and water- or heat-damaged tape each start from a different severity baseline. A phone voice memo is not the same restoration job as a damaged reel. ### The real processing order Impulsive noise like clicks and pops gets treated before broadband hiss. Hum is handled as its own tonal pass. De-reverb runs last, since it is the step most likely to introduce artifacts. ### Target quality changes the plan Archival or broadcast targets get a more conservative noise-reduction strength to protect naturalness. Casual listening can take a heavier hand. ## Three inputs, one plan 1. **Pick the source** — Cassette, vinyl, a phone voice memo, a field recording, an old low-bitrate digital file, or a water- or heat-damaged tape. This sets the difficulty baseline before any problems are added. 2. **Tick what you actually hear** — Hiss, hum, clicks, clipping, dropouts, reverb: check only what is audible in the file. Guessing at problems that are not there inflates the score and the recommended processing chain. 3. **Set the target quality** — Casual listening, podcast-ready, or archival and broadcast. This changes the suggested noise-reduction strength, since a heavier hand is fine for a commute but risky for a preservation copy. 4. **Read the plan** — The score, the tier, the processing order, an estimated turnaround, and a starting noise-reduction percentage update instantly as the answers change. ## Questions people ask before running this ### Is this free, and does it upload my audio file? It's free and nothing uploads. The score, the processing order, and the time estimate are all computed in your browser from the answers you tick, not from the audio file itself. ### Where do the difficulty weights come from? From standard audio restoration practice: impulsive noise (clicks, pops) is treated before broadband hiss, hum gets its own tonal pass, and de-reverb runs last because it is the step most likely to add artifacts. Source baselines reflect how condition typically varies by format: a damaged tape starts worse than a low-bitrate digital file. ### Why does target quality change the noise-reduction percentage? A higher reduction strength removes more noise but risks a processed, unnatural sound. Archival and broadcast work needs that risk kept low, so the suggested strength drops. Casual listening tolerates a heavier pass. ### Can I use this before I buy restoration software or hire someone? Yes. That is the point: get a realistic sense of the tier (light, moderate, heavy, or professional-grade) before you commit budget or software licenses to the job. ### Does the score account for how long the recording is? Length does not change the difficulty score itself, since difficulty is about condition, not duration. It does drive the estimated processing time, which scales with both the tier and the minutes of audio. ### What if none of the listed problems match what I'm hearing? Leave every checkbox unticked and the tool falls back to a light normalize-and-denoise recommendation, which covers most clean-ish digital sources. ### Is 100 the worst possible score? Yes, the score is capped at 100. A water-damaged tape with hiss, hum, clicks, clipping, dropouts, and reverb, restored to archival quality, will hit that ceiling. That result is a signal to bring in a specialist rather than push AI tools past what they handle well. ### Does heartheweb do audio restoration itself? No. heartheweb turns written articles into a clean MP3 feed for listening while you commute or when screens are not an option. This calculator exists because narration fidelity and audio cleanup share the same underlying questions about noise and quality. ## Curious what heartheweb actually sounds like? heartheweb turns your reading list into a private MP3 feed, narrated cleanly, for the commute or the moments a screen is not available. *Call to action: Explore heartheweb* ## FAQ ### Is this free, and does it upload my audio file? It's free and nothing uploads. The score, the processing order, and the time estimate are all computed in your browser from the answers you tick, not from the audio file itself. ### Where do the difficulty weights come from? From standard audio restoration practice: impulsive noise (clicks, pops) is treated before broadband hiss, hum gets its own tonal pass, and de-reverb runs last because it is the step most likely to add artifacts. Source baselines reflect how condition typically varies by format: a damaged tape starts worse than a low-bitrate digital file. ### Why does target quality change the noise-reduction percentage? A higher reduction strength removes more noise but risks a processed, unnatural sound. Archival and broadcast work needs that risk kept low, so the suggested strength drops. Casual listening tolerates a heavier pass. ### Can I use this before I buy restoration software or hire someone? Yes. That is the point: get a realistic sense of the tier (light, moderate, heavy, or professional-grade) before you commit budget or software licenses to the job. ### Does the score account for how long the recording is? Length does not change the difficulty score itself, since difficulty is about condition, not duration. It does drive the estimated processing time, which scales with both the tier and the minutes of audio. ### What if none of the listed problems match what I'm hearing? Leave every checkbox unticked and the tool falls back to a light normalize-and-denoise recommendation, which covers most clean-ish digital sources. ### Is 100 the worst possible score? Yes, the score is capped at 100. A water-damaged tape with hiss, hum, clicks, clipping, dropouts, and reverb, restored to archival quality, will hit that ceiling. That result is a signal to bring in a specialist rather than push AI tools past what they handle well. ### Does heartheweb do audio restoration itself? No. heartheweb turns written articles into a clean MP3 feed for listening while you commute or when screens are not an option. This calculator exists because narration fidelity and audio cleanup share the same underlying questions about noise and quality. --- ### Excel Formula Generator: Find the Right Formula Fast URL: https://heartheweb.com/tools/excel-formula-generator > Describe the spreadsheet task and get the exact formula, explained argument by argument, for Excel 365, Excel 2016-2019, and Google Sheets. ## Excel Formula Generator: Find the Right Formula Fast Describe the spreadsheet task once. Get the real VLOOKUP, SUMIF, INDEX MATCH, or IF syntax, explained argument by argument, plus the Excel 2016 and Google Sheets version when it differs. ## Excel and Google Sheets formula generator Pick what you are trying to do and which spreadsheet you are using. The formula updates instantly below, ready to copy into your cell. *[Interactive widget — see the live page for the full experience]* ## What goes into each formula ### Real formulas, not guesses Every formula in this generator is standard Excel or Google Sheets syntax, the same syntax documented by Microsoft and Google. Twelve common spreadsheet tasks, three spreadsheet versions each. ### Version-aware output XLOOKUP and UNIQUE only exist in Excel 365 and Google Sheets. Pick Excel 2016-2019 and the generator swaps in the VLOOKUP or COUNTIF workaround that actually runs there. ### Copy and go Hit copy, paste into your cell, then swap the cell references for your own range. The argument breakdown underneath tells you exactly what to change. ## How to use this generator 1. **Pick your task** — Choose what you are trying to do from the list: a lookup, a conditional sum, a text join, a date calculation, or one of eight other common jobs. 2. **Pick your spreadsheet** — Excel 365, Excel 2016-2019, or Google Sheets. The formula and the explanation both adjust, since not every function exists in every version. 3. **Copy the formula** — The formula box updates the instant you change either dropdown. Copy it, paste it into your sheet, and swap the cell references for your own range. *Sample output* ## Three real formulas this generator writes for you A lookup across two tables, a conditional sum with two criteria, and a date calculation between two columns: these are three of the spreadsheet questions that come up most in office chats and support tickets. Below is what the generator returns for each one, using Excel 365 syntax. Switch the version dropdown in the tool above and the same three tasks return Excel 2016 or Google Sheets syntax instead. - Lookup: =XLOOKUP(B2, A2:A100, C2:C100, "Not found") - Conditional sum: =SUMIFS(D2:D100, A2:A100, "Widgets", B2:B100, ">100") - Date difference: =DATEDIF(A2, B2, "d") - Each one comes with an argument-by-argument breakdown in the tool above ## Common questions ### Is this Excel formula generator free to use? Yes. It runs entirely in your browser. Nothing you type is stored or sent anywhere. ### Does it work for Google Sheets too? Most of the time. Select Google Sheets in the second dropdown and the generator swaps in Sheets syntax where it differs from Excel, like UNIQUE or TEXTJOIN support. ### Why does the formula change when I pick a different spreadsheet version? Because it should. XLOOKUP and UNIQUE only work in Excel 365, Excel 2021, and Google Sheets. Excel 2016-2019 needs VLOOKUP, INDEX MATCH, or a COUNTIF workaround instead, and this generator gives you the version that actually runs. ### Where do these formulas come from? Standard Excel and Google Sheets function syntax, the same syntax documented by Microsoft and Google. Nothing here is a shortcut or an approximation. ### What if the copy button does not work on my browser? Select the text inside the formula box and copy it manually with Ctrl+C or Cmd+C. Every formula stays visible on screen, so nothing is hidden behind the button. ### Can I use this on my phone during a commute? Yes, the dropdowns and formula box are built mobile-first. It is a fast reference if you are between trains and need the syntax before you forget it. ### Does this replace learning Excel? No. It gets you the right formula fast for a specific task. For the reasoning behind SUMIF versus SUMIFS, or why INDEX MATCH beats VLOOKUP, sites like Exceljet and Contextures go deeper. ### Why is not there a formula for my exact situation? This generator covers twelve of the most common spreadsheet tasks: lookups, conditional sums and counts, text joins, date math, unique values, conditionals, and error handling. It will not cover every edge case, but it covers what most people search for. ## Need more than one formula a day? Formula.dog is built specifically for people who live in spreadsheets: real Excel and Sheets syntax, explained the same way, any time you need it. *Call to action: Visit formula.dog* ## FAQ ### Is this Excel formula generator free to use? Yes. It runs entirely in your browser. Nothing you type is stored or sent anywhere. ### Does it work for Google Sheets too? Most of the time. Select Google Sheets in the second dropdown and the generator swaps in Sheets syntax where it differs from Excel, like UNIQUE or TEXTJOIN support. ### Why does the formula change when I pick a different spreadsheet version? Because it should. XLOOKUP and UNIQUE only work in Excel 365, Excel 2021, and Google Sheets. Excel 2016-2019 needs VLOOKUP, INDEX MATCH, or a COUNTIF workaround instead, and this generator gives you the version that actually runs. ### Where do these formulas come from? Standard Excel and Google Sheets function syntax, the same syntax documented by Microsoft and Google. Nothing here is a shortcut or an approximation. ### What if the copy button does not work on my browser? Select the text inside the formula box and copy it manually with Ctrl+C or Cmd+C. Every formula stays visible on screen, so nothing is hidden behind the button. ### Can I use this on my phone during a commute? Yes, the dropdowns and formula box are built mobile-first. It is a fast reference if you are between trains and need the syntax before you forget it. ### Does this replace learning Excel? No. It gets you the right formula fast for a specific task. For the reasoning behind SUMIF versus SUMIFS, or why INDEX MATCH beats VLOOKUP, sites like Exceljet and Contextures go deeper. ### Why is not there a formula for my exact situation? This generator covers twelve of the most common spreadsheet tasks: lookups, conditional sums and counts, text joins, date math, unique values, conditionals, and error handling. It will not cover every edge case, but it covers what most people search for. ---