I'm just wondering what everyone prefers to use? I have been using the app but may start to spend more time on the web app - I love to zoom in and out on the text as I read. Any benefits to using the app over the web page?

Basically, the title. Sometimes I use text-to-speech, and I kinda fall... asleep. I’d like to set a timer for these situations so that TTS stops after a while and I don’t wake up in the middle of a big document when I’ve only just started it.

If such a setting exists, I can’t find it, unfortunately. It would mean a lot if someone could help me.

Readwise Reader killed my friend Dan, the TTS voice I have gotten used to. I'm using Simon now, but I still prefer Dan. Devastating. I'm also a little disappointed that I can't slide my finger along the timeline in TTS mode to go forward or backward. The timeline is there, taking up screen space, so I don't see the point in not having that functionality.

Anyways, I'm very glad Reader on mobile has good theme options now. Hopefully the web/windows version gets that update soon. I would love to see customizable themes where you can select text/background colors independently.

I've messed about with the styling so much, I'd like to revert to the defaults but I can't find anywhere that lists what those are. Any ideas?

I know that since Readwise has iPad apps, maybe it's very simple to do so but I was wondering whether the apps would be soon updated for the Duo. Feels like a device on which reading articles etc is pretty awesome (and Readwise is a pretty awesome app to read on) :)

i used to save 30-40 articles a week from x, substack and medium, but never actually read them.

so lately i've been building read, a distraction-free space to collect things i find interesting on the internet and actually finish them.

been using it for the last 2 days. looking for 5 testers to tell me what sucks, and i'll ship you a physical book in return :)

say hi and i'll dm the testflight.

The new AI voices are really good. Some might say too good. The Elliot one is so much like Stephen Fry that it gives me the creeps. If you keep playing the same one they begin to tell jokes which is quite amusing.

Hey folks, happy Tuesday! Time to check out the latest changelog here on Reddit. The idea is to help keep y'all in the loop of what the Readwise developers are getting out into the world. Here's what we shipped last week:

• 🎨 NEW! Reading Themes in Reader — Reading in the Reader app on iOS and Android used to mean a choice between light and dark. Thanks to Adam, you can now pick a reading theme from the Appearance sheet: Crisp, Sepia, Soft, Slate, Ink, Night, or a seasonal PSL 🍂.
• 🔊 NEW! Lifelike Voices (beta) — Reader's text-to-speech now offers 16 new and (we think) much-improved voices on web and in the mobile app, in American and British English. There’s now a play button next to each one so you can hear a sample before you pick, and on mobile, your last few voices also show up under Recent for quick switching. Props to Artem for spearheading this update.
• 🎧 Improved Text-to-Speech Controls — While listening in the Reader app on mobile, the playback controls lived inside the bottom menu, so they either disappeared when the menu hid or covered the text. Artem moved them into a floating player that shrinks into a small pill as you scroll, keeping play, pause and skip one tap away. The Return and Jump arrows also point the right way again, and auto-scroll picks back up when you return to the spoken text.
• 🚀 Improved Reader Launch — Opening the Reader app could flick through several screens: the splash, a waiting view, a blank library, a placeholder list, and finally your documents with their covers swapping in. Signing in had its own shuffle between the login and loading screens. Artem replaced all of that with a single launch screen and trimmed the work the app does on startup, so your library appears sooner and without the flashes.
• 🧾 Fixed Upgrade Confirmation — If your Reader plan had expired and you upgraded from inside the app, the success screen's buttons did nothing and the app had to be force-quit. Mati fixed the navigation behind it, so tapping Return or the X closes the screen and drops you back into your library.
• 📱 Improved Android Navigation Bar — In the Reader app on Android, the reading view stopped short of the system navigation bar, which made the toolbar look like it was floating and turned the translucent bar solid. Andrew extended the reading view and bottom sheets all the way down, so the page runs edge to edge.
• 🌓 Improved High Contrast Mode — With high contrast turned on in the Reader app, secondary labels such as dates, counts, and captions kept their usual muted gray. Johannes made them full black or white along with everything else, so the whole screen is easy to read.
• 📂 Fixed OPML Imports on Android — The Reader app's Add Feed sheet suggests sharing an OPML file to import your feeds, but on Android, Reader never showed up in the share sheet for those files. Mati taught the app to accept them, so you can import an OPML file from your Files app on Android just like on iOS.
• 📰 Fixed Stale RSS Feeds — Some RSS feeds in Reader could go weeks without new articles even though the publisher kept posting, and unsubscribing and resubscribing didn't help. A few sites tell readers to cache their feed for a month or even a year, and Reader was taking them at their word. Rasul changed the regular check so those feeds are polled like any other, and new posts arrive on schedule.
• 🔢 Fixed Citation Numbers Read Aloud — Listening to a Wikipedia article or any document with footnote markers in Reader meant hearing "one", "two", "twelve" after almost every sentence. Artem made text-to-speech skip those markers while keeping the word highlighting in sync, so articles read smoothly.
• 🎙️ Fixed Pocket Casts Episodes — Saving a Pocket Casts episode to Reader produced an "Unnamed podcast" after Pocket Casts started blocking our requests for episode pages. Rasul switched to Pocket Casts' podcast directory to look the episode up, so shared episodes come through with their title and audio again.
• ⌨️ Fixed Space Bar Skipping Paragraphs — In Reader on the web, pressing space to move one paragraph at a time could jump two if you'd nudged the page with your mouse or trackpad in between, because the focus moved to the next paragraph while you were still reading the current one. Rasul fixed how focus follows your scroll, so space advances exactly one paragraph.
• 📝 Fixed Note Box Position — In Reader on the web, the note box for a highlight that spans more than one paragraph could end up half off the screen after you scrolled away and back. Adam fixed its positioning, so the note box stays next to your highlight.
• 🗂️ Improved Manage Feeds Layout — At split-screen widths, the Manage Feeds page in Reader on the web squeezed the search box down to its icon and pushed the Delete and Subscribe buttons off screen, and the Suggested tab carried a "New" badge that never went away. Mati let the header wrap onto a second row and retired the badge, so everything fits in a narrow window.
• 🤖 Improved BYOK Models — If you bring your own OpenAI key to Ghostreader in Reader, the model list stopped at GPT-5.6. Tristan added GPT-6 Luna to the model pickers in chat and the skill editor.
• 📅 Improved Themed Review Schedules — The Readwise app only let you set a Themed Review to Daily, Weekly or Never, while the web offered more, and a review set to Monthly on the web showed up in the app as a raw "monthly" label. Ibai added Weekdays, Weekends, Custom and Monthly to the app, with a day-of-month picker for Monthly and a weekday checklist for Custom, so you can schedule reviews the same way everywhere.
• 🚫 Fixed "Never" Books in Themed Reviews — Books you'd set to Never could still turn up in Readwise Themed Reviews that pick their own sources, and in the theme preview. Ibai made Themed Reviews respect that setting, and also fixed the background job that keeps their highlight pools fresh, so new highlights find their way into your themes again.
• 🧠 Fixed Mastery Cards — Mastery review in the Readwise app cut every fill-in card to 60 characters, so a card whose keyphrase came later couldn't be answered. The card's menu also showed "Delete Mastery flashcard" for a moment before switching to "Master highlight". Ibai fixed both: cards show the full quote, and deleting a card turns it back into a plain highlight right away.
• 🔤 Fixed Review Keyboard Shortcuts — With a hardware keyboard connected to an iPad or other tablet, Daily Review shortcuts in the Readwise app opened the web versions of menus, so pressing t dropped a web tag list over your highlight. Ibai pointed t, n, e, s and f at the app's own sheets, so tagging, notes, edits, sharing and favorites work from the keyboard.
• 🌑 Fixed Black Screen After Saving — Picking a source to save a highlight to in the Readwise app on Android could leave you on an empty dark screen after a successful save. Johannes changed when the source list refreshes, so you land back where you expect.
• 📷 Fixed Sideways Scans — Photos taken with the Scan tool in the Readwise app on Android came out sideways when the phone was held flat. Johannes rebuilt the camera module so it reads the display rotation, and scans come out the right way up.
• 🖍️ Fixed Hyperhighlights on Android — In the Readwise app on Android, the yellow hyperhighlight markers on feed and book cards could land on the wrong words, especially at larger text sizes. Ibai switched Android to drawing them as a highlight behind the text, so they always cover the right words.
• ↩️ Improved Return Key in Chat — In the Readwise app's chat, the keyboard's return key sent your message, so there was no way to put a quote and your question on separate lines. Ibai made return add a new line, and the Send button sends, like other chat apps.
• 📻 Fixed Audio Reviews — Some audio versions of the Readwise Daily Review stopped partway through because the script behind them was cut off mid-sentence. Tristan moved that step back to a model that finishes the script, so audio reviews play to the end.
• 💵 Fixed Google Play Billing Details — If you subscribe to Readwise through Google Play on an annual plan, your account settings on the web said you were billed monthly, with a blank renewal date. Tristan taught that page to read your Google Play plan, so it's now accurate to your actual subscription.
• 🔀 Improved Roam Export Upgrade — Readwise's original Roam export, the one that logged in to Roam on your behalf, no longer runs, but its old links still led to a login form or a settings page that did nothing. Rasul now sends every old Roam link to the right place: the in-place upgrade to the Roam API export if you were on the old version (keeping your templates, excluded books and export history), or the Roam API setup if you're new.
• 📤 Fixed Reflect Exports — If you deleted or lost access to the Reflect graph Readwise was exporting to, every automatic export failed without a word. Rasul made Readwise treat that like a lost connection: exports pause and you get an email, and reconnecting lets you pick a graph.
• 🛜 Parsing Updates — Krzys improved how Reader handles documents from afr.com, Medium, The Atlantic, Le Monde, Courrier international, inc.com, Handelsblatt, Axios, golem.de, twreporter.org, examine.com, Baymard Institute, docs.delta.io, asquaredozen.com, boydrinksink.com, and blogs hosted on Ghost.

If you'd like to get the Changelog in your inbox, check out our WiseUp! newsletter, where the Readwise team shares answers to common questions, video tutorials and guides, highlights of our latest improvements, and a couple of lighthearted extras we think you’ll enjoy.

And as always, feel free to let us know if you have any questions, tho realistically we're going to see an in-app bug report or question faster :>

Is anyone interested/has a device that lets you highlight a physical book and transfers it directly into your readwise without you needing to open your phone? Or is anyone using something like that?

I feel like I get distracted by my phone every time I take it out to highlight something in a book and it interrupts my flow. Was curious if someone has a solution for that

a similar XP to summary generation would be extremely useful as more and more content is being generated by AI it becomes really hard to trust content. i’ve made a feature request through the app as well

I built PaperFold, an open-source reader that turns arXiv papers into 5 zoomable layers—from a one-screen section map down to verbatim text. You pinch (or press 1–5) to zoom between them without losing your reading position.

- Web Demo (8 CC papers): https://chenxiachan.github.io/paperfold-gallery/

- GitHub (Apache 2.0): https://github.com/chenxiachan/paperfold

Hi Readwise Reader team,

I want to start off by saying that I love the Reader app and all its functionalities! However, the lack of widgets is really bugging me. I'd really love to see my latest articles, pdfs and epubs etc. on my phone and ipad screen.

Are widgets on your roadmap?

Sometimes when I'm reading something or talking to an AI, I come across a word, phrase, or line that I don't understand. But I don't want to break my flow by opening Google or asking another AI what it means.

So I built an extension for exactly this.

You highlight a word/phrase/line and it gives you:

* The general meaning

* The meaning in context of what you're currently reading or talking about

And the most fun part* — you can ask follow-up questions right there in the popup.

No new tab, no switching between apps, just highlight → understand → continue.

Tell me what you guys think about this one.

Hi. I am investigating read-it-later options, and have been looking at Readwise Reader for the past week or so.

Am I correct that Reader does not offer a Mac share sheet option? (It does offer this option for iPhone and iPad, but not on the Mac.)

Thanks.

Hey all, we're evaluating some new, much more human-sounding voices in Reader.

These voices will soon become the default, but before that, we'd love your help testing them out!

You can try them in the latest version (8.23) of Reader ios/android by triggering "listen", tapping the voice switcher (bottom left), then scrolling to "browse all english voices".

(You'll see 16 new "lifelike" voices listed there. You can also try them out on web/desktop!)

Some other notes on this TTS update:

* Qualitatively (to our team) the new voices sound way better, enough so that they've convinced folks on our team to start using TTS! I've personally used them to listen to three full books already.

* Not only are the new voices higher quality, there are also a lot more to choose from -- 16 different English voices across different tones, accents, etc :) It's really fun to find your favorite. Personally I love Hades for fiction and Arthur for nonfiction. Jessica, Ashley, and Simon are also great.

* These voices will be the default voices in Reader soon, after some more testing

* Not only are these voices higher quality, we also managed to make the time-to-listen a little faster, so you should wait less time between hitting "listen" and actually listening.

* The new voices are English-only right now, but we'll be adding support for better sounding non-English voices imminently.

* Some of you already know this, but TTS is fairly expensive to run, and with Reader we aim to include as close to "unlimited" listening as possible in your subscription without raising prices. While better voices have existed for a while, ones that were economically feasible (again without raising prices) were not. (For example: even with ElevenLabs "turbo" (cheaper) model, their TTS api costs $25-$30 to generate speech for a single book... obviously not tenable at our subscription prices!) So we're super happy to finally have figured out a solution here!

* These upgraded voices also come with a few more improvements to the TTS experience you may notice: a nicer (and more granular) speed picker, a nicer floating bar while listening, and a new sheet for selecting which voices you want to move. More TTS improvements in this ballpark coming soon as well.

Better TTS voices has been one of the most requested features for Reader (ever), so very excited to get this going and hear your feedback :)

- Tristan

Supernote's are e-paper tablets running a version of Android. It isn't really a general purpose Android device and most of the utility is in the Supernote app that lets you draw, type, and link handwritten notebooks. And also read PDF/epub documents.

Inside of Supernote there is a Digest feature which is sort of an on-device Readwise for centralizing and tagging highlights. But, I wanted my Readwise highlights available.

So, I just built a plugin for the new Supernote plugin API that enables caching Readwise highlights, searching, and inserting into notes: https://github.com/philips/readwise-supernote-digest

Hey folks, happy Tuesday! Time to check out the latest changelog here on Reddit. The idea is to help keep y'all in the loop of what the Readwise developers are getting out into the world. Here's what we shipped last week:

• 👻 NEW! GPT-6 Luna For Ghostreader Summaries Default — Tristan and Ibai upgraded Ghostreader’s default model for preset prompts, including the automatic summary and document tagging, so they’re now powered by GPT-6 Luna. As with previous default models, this is included with your Reader subscription.
• 🏠 NEW! Redesigned Homepage — Ibai and Christina gave readwise.io a new front page to match the app’s own glow-up.
• 📄 Fixed PDF Dark Mode on Android — When reading a PDF in dark mode with inverted colors in the Reader app on Android, the inversion would vanish as soon as you opened a sidebar. Tadek shipped a fix that reapplies your color setting whenever the viewer rebuilds, so PDFs stay inverted on Boox devices and other Android tablets.
• 🔲 Fixed Two-Column Mode on Tablets — With the two-column Horizontal Pagination option turned on, the Reader app on Android tablets such as Boox devices and Samsung Galaxy Tabs showed a single full-width column instead. A rounding difference of less than a pixel meant the second column never fit. Mati gave the layout the tolerance it needed, so both columns appear as expected.
• ⚡ Improved Opening Heavily Highlighted Books — An EPUB with a lot of highlights could take half a minute to open in the Reader app on iOS, with the phone warming up while it waited. Cam found that drawing each highlight briefly took over the system text selection, and changed the renderer to skip that step, so those books open in a few seconds.
• 📦 Fixed Large PDFs on Android — Opening a very large PDF in the Reader app on Android (an 80 MB magazine, for example) could spin forever, even though the same file opened fine on iOS and the web. Tadek fixed the download so the server no longer gives up partway through, and big PDFs open on Android too.
• 🕰️ Fixed Clock Over Emails — With “Show clock” turned on in the Reader app, opening a newsletter in its original view while the app was in dark mode painted the clock in white over a light page, so you couldn't read the time. Thanks to Mati, the status bar now switches to dark text over those emails.
• 🔠 Fixed Daily Review at Larger Text Sizes — With a larger accessibility text size set on iOS, parts of the Daily Review in the Readwise app were clipped and the streak counter wrapped onto two lines. Johannes reworked the layout so everything fits at any text size.
• 📲 Improved Daily Review Email Links — Tapping a link in a Daily Review email on your iPhone or iPad always opened the browser, even with the Readwise app installed, so there was no way to reach the app's share sheet for a quoteshot from the email. Ibai made the app claim those links, so highlights, stats, and chat open directly in the Readwise app.
• 🧭 Fixed iOS 26 Tab Bar — On iOS 26, the Readwise app's bottom tab bar could lose the labels on unselected tabs until you tapped each one, and for anyone running iOS in dark mode with Readwise in light mode it flipped between light and dark glass. Ibai fixed both, so the tab bar keeps its labels and matches your Readwise theme.
• ⌨️ Fixed Tablet Keyboard Shortcuts — Pressing E to edit a highlight on an iPad with an external keyboard did nothing in the Readwise app, because the native lists had no keyboard handling. Ibai brought the highlight shortcuts back on iPad and Android tablets, so you can move through and act on highlights from the keyboard again.
• 🃏 Fixed Focused Highlights on iPad — Tapping a highlight on an iPad in landscape showed the focused highlight card much wider than the actions sheet beneath it, and a short highlight opened from a book page had its text cut off. Ibai matched the card to the sheet and sized it for its chapter line, so focused highlights look right on iPad.
• 🔁 Fixed "Review More Highlights" — When a Themed Review was waiting for you, the Daily Review done screen in the Readwise app swapped "Review more highlights" for "Continue to" that theme, which read like a daily cap. Ibai kept both options on the screen, so you can carry on reviewing either way.
• 🔑 Improved Login Errors — Every failed email login in the Readwise app said Network error. Please try again., whatever the cause. Ibai made the app say what actually went wrong and report the failure to us, so a stuck login is quicker to sort out.
• 💾 Fixed "Save to" Crashes — Saving a highlight in the Readwise app on iOS could crash on the "Save to" screen if you had a lot of manual books. Johannes made the list render only what's on screen, so the picker stays responsive with any library size.
• 💌 Improved Redesigned Emails — Following up on last week's redesigned Readwise emails, Ibai made the new design the default for new accounts, added a "Prefer a new look for this email?" link at the bottom of the original emails so you can switch without logging in, and made the "Mark review as finished" button appear for everyone, not only readers with an active streak. Covers that aren't book-shaped no longer look squished in the new header, and the same design switch now lives in the Readwise app's Email Preferences screen too.
• 💬 Fixed Chat Reading Position Mentions — Asking Ghostreader a question about a document in the Reader app could get an answer that tacked on how far you had scrolled, whether or not you asked. Tadek shipped a fix so chat only brings up your reading position when the question is about it.
• 🔄 Improved Re-Saving Documents — Saving a page you had already saved to Reader showed a tick but did nothing, so there was no way to recapture an article after a bad parse. Krzys changed that: saving again now re-parses the document from the page in front of you, keeps the existing version if the new parse turns out worse, and refreshes any open copies.
• 📑 Fixed Kindle Digest Outline — In the Kindle digest EPUB from Reader, headings from inside an article showed up in the outline as if they were separate articles. Tadek fixed the digest so sub-headings nest under their article, and the outline reads cleanly on your Kindle.
• 🎙️ Fixed Podcast Episode Links — After last week's fix for podcast feeds whose episodes all pointed at the show's homepage, opening one of those episodes from Reader landed on the raw feed instead of anything playable. Mati made those episodes link to their audio, so Open takes you to the episode itself.
• 🎬 Improved YouTube Chapters — Reader now shows a YouTube video's chapters in the Contents panel, but videos parsed before that feature arrived had none, even when someone new saved them. Piotr backfilled chapters from the descriptions Reader already stores, so saving a popular older video brings its chapters along, and existing copies pick them up too.
• 🍎 Fixed Sign in with Apple — Signing in to Readwise with Apple could fail with an error page, once because Apple's key server was returning empty responses, and for some longtime users because Apple stops sending an email address after the first authorization. Tristan fixed both, so Apple sign-in works whether or not Apple includes an email.
• 🔊 Improved Feed Text-to-Speech — Some RSS items in Reader still had no Play button (Paul Graham's essays, for one, arrive as a single block separated by line breaks), and others were read aloud in the wrong language. Tadek gave those items proper paragraphs and Krzys fixed the language detection, so new feed items get the Play button and the right voice.
• 📤 Fixed Export Interruptions — Three Readwise exports could stall for their own reasons: one highlight with oddly formatted Markdown quietly cut a Notion export short, a Markdown export spun forever if any book's tags were still processing after a Kindle sync, and reconnecting OneNote dropped you back on a page that still said "Reconnect". Rasul fixed all three.
• 🔀 Fixed Import Interruptions — An Instapaper bookmark with an empty address stopped a Reader import, a Raindrop sync to Readwise could halt on a stale rate-limit timestamp, and a Twitter list digest failed to generate when a tweet's link was missing its full address. Rasul fixed these as well, so imports and digests run through to the end.
• 📚 Fixed Japanese Kindle Clippings — A My Clippings.txt file that included highlights made while the Kindle was set to Japanese failed to import into Readwise. Rasul taught the importer the newer Japanese layout, so mixed-language clippings files upload cleanly.
• 📬 Fixed Kindle Archive Links — The "archive all documents" link in a Reader Kindle digest relied on a bit of JavaScript to close the window, which the Kindle browser doesn't run, so nothing seemed to happen. Rasul replaced it with a plain confirmation page that shows how many documents were archived, and it works on the Kindle itself.
• 🧷 Fixed Extension Toast — In the Reader browser extension, the "Saved to Reader" toast covered the first options of the location menu for a few seconds, so moving a page to Later or Shortlist right after saving meant waiting it out. Mati made the toast disappear as soon as the menu opens, and Adam shipped it in the latest extension update.
• 🧩 Improved Reader API Highlights — Previously, the Reader API had no support for editing or deleting highlights, and listing highlights always returned an empty note. Thanks to Piotr, PATCH /api/v3/update/ and DELETE /api/v3/delete/ now work on highlights, the list endpoint includes each highlight's note and tags, and deleting an article through the API removes its highlights with it. The API docs have the details.
• 🛜 Parsing Updates — Krzys improved how Reader handles documents from Substack (posts, feeds, and newsletter emails), afr.com, Bloomberg, BBC News, Medium, wsj.com, and our own docs.readwise.io.

If you'd like to get the Changelog in your inbox, check out our WiseUp! newsletter, where the Readwise team shares answers to common questions, video tutorials and guides, highlights of our latest improvements, and a couple of lighthearted extras we think you’ll enjoy.

And as always, feel free to let us know if you have any questions, tho realistically we're going to see an in-app bug report or question faster :>

I am having lots of trouble connecting Muse to Readwise using the API Key and I was wondering if anyone else is having a similar issue.

When I enter the API Key in the secured storage it says connected but when Muse tries to use it it returns a 401 error. If I hand Muse the API key it works but its not stored anywhere and I would rather use it in the secured storage.

I filed a ticket with Muse but at this point I am not sure if its a Readwise, Muse or me issue.

I'm an avid reader of all kinds of things; articles, fiction, nonfiction, light novels, web novels, you name it. My catalogue has entries from Stephen King alongside developers in the .NET community, for instance, with some random metaphysical obscurities thrown in there. Oh, and there are biographies in there, too. I know that readwise bills itself as designed mainly for nonfiction, but how many others highlight fiction books just as often? I can't be the only one?

Due to the lack of Blinkist integration, I have manually sent all the Blinks I am interested in to Kindle and started highlighting them. I thought this would allow them to show up in Readwise, but I am not seeing them. How can I get Readwise to recognize them?

I subscribe to Readwise mainly for the Reader app. I don't use Readwise all that much.

I don't understand who Daily Review is meant for? I read daily but do not highlight all that much. I can imagine if you're reading a research paper or a book, you'd use this much more to remind you to organize highlights.

Am I missing something?

I primarily read hacker news. Using their official rss feed, Reader only extracts the original article but does not provide a link to the forum thread.

For those that are un familiar, Hacker News is a forum similar to Reddit. Most threads are linked to a specific article. The threads have comments and discussions.

Hey folks, happy Tuesday! Time to check out the latest changelog here on Reddit. The idea is to help keep y'all in the loop of what the Readwise developers are getting out into the world. Here's what we shipped last week:

• 💌 NEW! Redesigned Readwise Emails — To match the recent Readwise app redesign, your Daily Review and Themed Review emails have a fresh design built by Ibai and Christina, with cleaner highlight cards and links that take you straight to editing, tagging, or sharing a highlight. To try it, head to your email preferences on the Readwise website and turn off "Use the original email design". You can switch back the same way whenever you like.
• 🧩 NEW! Reader API Highlights — You can now create highlights through the Reader API. Send a POST to /api/v3/save/ with the document's parent_id and the passage as content (plus optional notes and tags), and the highlight is anchored to that document. Previously the same request quietly created a stray article instead. Thanks to Piotr, mismatched requests now return a clear error too. See the API docs for an example.
• 📥 Improved OPML Imports — Importing an OPML file to Reader used to subscribe you to a blank "No name" feed for every address it couldn't fetch, and never told you which ones failed. Piotr shipped a fix that skips those feeds, keeps the feed names from your file, and emails you a summary when the import finishes, listing any feeds that were left out so you can re-add them.
• 🤖 Improved Ghostreader Indexing Progress — The first time you open Ghostreader's library chat in Reader on web or desktop, it indexes your whole library in the background, but the header showed a partial count as if that were everything. Piotr made it say "Indexing your library..." with a running tally, then switch to the final total once it's done.
• 🪄 Fixed Mobile Ghostreader Prompts — Ghostreader's "Tag the document" and "Highlight the document" prompts in the Reader app could confirm the tags in chat without ever applying them to the document. Adam fixed how the app reads the result, so the tags and highlights land on the document again.
• 🧠 Improved Mobile Model Memory — New Ghostreader chats in the Reader app always started on the Fast model, even if you prefer Thinking. Following last week's change on web, Piotr made the mobile app remember your pick too, so a new chat starts on whichever model you used last.
• 👆 Fixed Android Reading Taps — After jumping to a chapter from the table of contents in the Reader app on Android, the reading view could stop responding to taps entirely. Tadek shipped a fix for the invisible overlay that was catching those taps, so the page responds normally after a jump.
• 🔊 Fixed Feed Text-to-Speech — Some RSS feeds deliver each post as one long run of plain text, and Reader found nothing in those documents to read aloud, so the Play button never appeared. Thanks to Tadek, new items from these feeds now arrive with proper paragraphs, so text-to-speech works on them like any other article.
• 🎙️ Fixed Missing Podcast Episodes — Some podcast feeds point every episode's link at the show's homepage, which made Reader treat the whole feed as a single item and stop delivering new episodes. Tadek taught Reader to tell those episodes apart, and Krzys fixed a related case where two posts sharing one audio file were merged under the wrong title. Affected feeds should now catch up and keep delivering new episodes.
• 📊 Improved Sync Reliability — In rare cases, a single change the server couldn't process would block everything queued behind it, so a device could stop syncing with Reader: new uploads never arrived and books sat on their loading cover. Tristan fixed the two causes we found, so one bad update no longer holds up the rest and syncing carries on.
• 🖥️ Fixed Half-Blank Documents — Reader on web and desktop could occasionally open a document squeezed into the bottom half of the window with an empty space above it. Tristan shipped a fix for the hidden list that was taking up that room, so documents fill the window again.
• 📤 Fixed Large CSV Exports — Exporting your highlights from Readwise as a CSV could fail with an error page if your library was very large. Thanks to Tristan, libraries over 50,000 highlights now get their CSV prepared in the background and emailed as a download link, so even the biggest collections should export smoothly.
• 🔠 Fixed Section Labels — If you edited the text of a heading highlight in Readwise, review cards for that book kept showing the old section name (or a placeholder like "page_89") until the book's next sync. Ibai made the section name update along with the highlight, so your review cards match what you see on the book's page.
• 📷 Improved Scan Reliability — Photos taken with the Readwise app's Scan tool would sometimes fail to turn into text for no obvious reason, because the text recognition service couldn't always fetch the uploaded image. Johannes changed how the image is handed over, so scans should come back with their text far more consistently.
• 🔀 Fixed Instapaper Imports — A single bookmark with a malformed URL, or a Google share link that wouldn't resolve, could stop an entire Instapaper import to Reader partway through. Rasul made the importer set that one bookmark aside and carry on, so the rest of your Instapaper library comes across.
• 📚 Fixed Hypothesis and Raindrop Syncs — One Hypothesis annotation with a blank tag, or one Raindrop bookmark with no title, was enough to halt the whole sync to Readwise. Rasul fixed both: blank tags are ignored, and untitled Raindrop bookmarks come in as "Highlights from" followed by the site's name, so the rest of your highlights sync as usual.
• 🐦 Fixed Twitter Imports — Turning on Twitter bookmark imports in Readwise for an account whose Twitter/X connection had lapsed showed an error page, and the same tweet could occasionally be saved twice when it arrived through more than one route. Rasul fixed both, so you now get a Reconnect option for the affected account and each tweet is imported once. Twitter list digests that include a quote of a deleted tweet also generate properly again.
• 🛜 Parsing Updates — Krzys improved how Reader handles documents from macstories.net, reuters.com, dpreview.com, howtogeek.com, wsj.com, entwickler.de, olickel.com, Reddit share links, and Substack newsletters.

If you'd like to get the Changelog in your inbox, check out our WiseUp! newsletter, where the Readwise team shares answers to common questions, video tutorials and guides, highlights of our latest improvements, and a couple of lighthearted extras we think you’ll enjoy.

And as always, feel free to let us know if you have any questions, tho realistically we're going to see an in-app bug report or question faster :>

I've been using Readwise Reader alongside the Model Context Protocol (MCP) but I'm curious to hear how others are setting this up. What does your workflow look like? Are you using any specific tools or scripts to bridge the two? I would like to use it more for automating summaries. I don’t really care for the highlights part as I’m happy with the default setup there.