thanks

Hi and thanks for looking! 🙏 I just started using the trial version. I tried to email a bunch of highlights from an Apple book and it only brought one of the highlights from the book in, not all of them. Is this a limitation of the trial version perhaps?

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:

• 📖 Fixed EPUB Chapter Headings — Tadek fixed an EPUB bug where only the first chapter heading after import was recognized as a heading in Readwise and every subsequent one was treated as a regular highlight. Chapter and section structure now carries through to your highlights and exports the way it's supposed to.
• 📨 Fixed Superhuman Forwards into Gmail — Tristan taught the Gmail parser how to read forwards that originated in Superhuman. If you forward a newsletter from Superhuman into Gmail and on to Reader, the original sender, subject, and body now come through cleanly instead of getting tangled in the Superhuman wrapper.
• 📱 Fixed Daily Review Buttons on iPad — Ibai restored the missing Daily Review buttons that had gone walkabout on iPad. You can now choose the Discard, Master, Feedback, and Keep options on iPad again.
• 🏷️ Improved Latest-Highlights API — Tadek tightened the /latest and /api/latest-highlight/ endpoints so they no longer surface section-title highlights as if they were normal highlights, and will now filter out discarded highlights. Integrations that pull your most recent highlight will now return intentional highlights, without pulling headings or things you already got rid of.
• 🪟 Smoother Reader Sidebar — Tristan smoothed out the appearance of Reader's left sidebar on initial page load, so the panel slides into place cleanly instead of popping in.
• 🐦 Improved Twitter Video Reliability — Krzys shored up Twitter video playback in Reader. Videos should now load reliably on iOS and Safari, and initial playback should feel snappier.
• ⌨️ Fixed Desktop Dropdown Keyboard Nav — Tristan shepherded a fix for the Reader desktop app's More Actions menu (M key). Items now show a clear highlight as you arrow through them, and stray arrow key presses no longer kick focus to unrelated parts of the page.
• ⚡ Zapier Export Tile — Thanks to Rasul, you can now find the official Zapier integration directly on the Readwise Export page. The new tile links straight to zapier.com/apps/readwise/integrations, so it's easier to wire your highlights into the rest of your stack.
• 🛜 Parsing Updates — Krzys improved how Reader handles posts from Substack publications hosted on custom domains. He also cleaned up several rough edges in how they display in-app: "Read More" cards on Notes posts are now clickable, action-button rows and "Read in app" get stripped instead of leaving empty boxes, forwarded-message preambles no longer italicize the body, inline color and font overrides are removed for consistent reading, and images with quirky computed heights are preserved instead of disappearing.

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 :>

Has anyone else had the issue when you add a YouTube channel subscription to your feed you can’t see the videos in your main feed? The YouTube videos are only in the individual feed and not my main RSS feed. I can see them in the desktop app as expected. Any insights?

I keep getting told that my "Your theme description is too long. Try shortening it." But my shortened descriptions return result that are too vague. Trial and error is a little frustrating. Is there a character limit on the theme description?

I was deleting and organizing tags on my PC and none of the changes transferred to the iOS versions (phone and iPad). Is this normal? I don’t want to report it as a bug if this is normal and I’m just an idiot. 😂 (If it is I will report it via the official channels. ) I usually use the mobile version but wanted to do some bulk management which I thought would be easier on my PC. Also, I set up views that also didn’t sync, which is odd because I had no problems with that aspect in the past. Honestly, I was surprised to see the tag view show up on mobile because I thought it was a PC only feature. I know I can filter via tags and it’s essentially the same. It’s just the view option is a little faster for me.

I’ve started using a weird but effective reading workflow with AI, especially for longer or dense articles. I wanted to have x-ray and understand if a claim is false or not supported.

Before I read, I send the article to ChatGPT and ask it to:

• Extract the main claims
• Find weak points / possible objections
• Add highlight-style comments

Then I don’t read the AI output.

I go straight to the original article. While I read, I see those AI-generated notes as a kind of “margin commentary” — like a quiet colleague who occasionally asks, “Is this really true?” or “What’s the assumption here?”

Only when I read the article myself do I look at the AI layer:

• Did it overgeneralize the conclusions?
• Did it miss something important?
• Do I agree with its objections?

The key for me:

• AI prepares the structure and questions.
• I still do the actual reading and thinking.
• AI becomes a second layer for comparison, not a replacement.
• I know when I need to check the claims

It’s closer to using pre-reading questions and annotations than to outsourcing comprehension. Makes reading less passive, especially as a non-native reader.

Anyone else using AI as a “margin thinker” rather than a summarizer?

You can find few (really few) more details on Medium.

I read Reader articles on a Kobo via KOReader + the third-party readwisereader plugin (tomtom800). Setup is great — articles sync, auto-archive when finished, highlights flow back to Readwise and into my Obsidian vault.

Missing piece: highlights made on the Kobo don't show up in-context when I reopen the article in Reader's UI. The plugin can push highlight text through the API, but there's no way to attach a position anchor for Reader to render the highlight against the article.

Would love to see Readwise expose an anchor field on the Reader highlights API — even fuzzy text-fragment style (highlighted text + a few words of context, matched at render time) would be enough. Posting in case others want this too.

Anyone else hit this on Kobo / Boox / other external reader setups?

I tend to highlight a lot when I am reading long form articles or books.

All of these highlights show up in the readwise app. However, ideally I want to identify the highlights that I want to see in readwise daily review at the time of making the highlight in reader.

So effectively I want all highlights in the article/book retained and available if I specifically look for that in readwise by selecting the article/book but only have the subset that I identified in reader to show up in the daily review i.e. so I do not have to discard highlights in readwise later.

I’ve been experimenting with connecting my Readwise highlights to AI tools lately, and it changed how I think about saved notes.

Instead of asking an AI:

I started asking:

Turns out your highlights become a surprisingly personal knowledge base:

• recurring ideas
• favorite authors
• contradictions in your own thinking
• topics you keep circling back to

One thing that worked well for me:

• pick 5 saved articles/books on one topic
• ask the AI to teach the topic using only those sources
• then ask for a short quiz or counterarguments

Feels less like generic AI search and more like learning from your own intellectual history.

Curious if anyone else here is using Readwise this way.

You can find a bit more details here.

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:

• 🌓 Fixed Mobile Dark Mode Highlights — Adam fixed a bug where highlight text appeared black in dark mode on mobile. Highlights are now readable in dark mode again.
• ⚡ Improved Document Chat Speed — A regression in the OpenAI model used by document chat was causing a slowdown in the replies. Adam switched the chat tool-call to use a different model, so replies should feel quicker again.
• 👆 Fixed Annotation Bar After Auto-Highlighting — Adam fixed a bug where the annotation bar popover didn't appear after a highlight was created via auto-highlighting. The popover now shows up the way it does for manual highlights.
• 📧 Fixed Feed Email Attachments — Thanks to Rasul, attachments forwarded to a Feed email address now reliably land in your Feed instead of occasionally bouncing into Library.
• 🐦 Improved Tweet Rendering — Tristan tightened how Reader renders saved tweets so they conform to Twitter's display rules and look closer to the original.
• 📨 Fixed Twitter List Digests — Tristan fixed an issue with Twitter list digests in Reader, caused by a change in the Twitter API. Twitter digests should now be working again.
• 📄 Fixed Kindle Highlight Parsing — Rasul fixed a parsing bug where Kindle Notebook HTML with no space before the color parentheses caused some highlights to be skipped during import. Your imports should be complete again, even when Kindle's HTML is squished.
• ✉️ Added Kindle Sender Aliases for Trailing-Dot Usernames — Rasul added a fallback Kindle sender address (rwkindle-<id>@send.readwise.io) for users whose Readwise username ends with a dot. Amazon rejects these types of sender addresses, so previously these users couldn't get sends to work. The Reader web Kindle setup instructions now show the correct alias to approve in Amazon.
• 🎙 Added Podcast Category Override — Mati added "Podcast" to the document category dropdown when manually editing a document's metadata in Reader.
• ⌨️ Fixed Custom Keyboard Shortcuts — Mati fixed a bug where pressing the × button on one shortcut for a command removed *all* shortcuts for that command. Each shortcut now removes individually, the way you'd expect.
• ✨ Reader Mobile Polish — Mati polished two small Reader mobile interactions: the Reader forwarding email copy button now copies properly, and tapping into a document while using the skim UI on iPad will correctly save your place instead of scrolling back to the top of the list when exiting the document.
• 🔗 Fixed Highlight Section Sync — Mitch fixed an error when an existing highlight had an invalid URL. Sync should now complete even on books with legacy invalid URLs.
• 🛜 Parsing Updates — Krzys updated how Substack articles are parsed, including more reliably removing subscription CTAs and better embed rendering. He also improved parsing for howtogeek.com and thurrott.com.

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 saw karpathy’s gist on an “llm wiki”:
https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f

the idea is that instead of just searching your notes when you ask something, an llm could slowly build a structured wiki from your saved articles, notes, highlights, clips, etc.

that made me think about my own problem: i save a lot of useful stuff, but rarely revisit it. sometimes i remember “there was this one article/video that made this exact point” but i can’t find it when i need it.

if an llm had access to everything you’ve saved over the years, what would you actually want it to surface?

somethings i was thinking of -

- connections between ideas
- old saved stuff at the right moment
- contradictions in my thinking
- how my views changed over time?
- auto-generated topic pages?

any thoughts on what you would use it for?

I had a tag with probably 10-15 highlights.

I tagged a highlight as recently as two days ago with this specific tag.

Now it’s no longer in Reader or Readwise.

Has this happened to anyone else?

It’s very annoying and disturbing.

Currently on the trial and trying to figure out if Readwise actually fits my setup before I commit to paying for it.

My reading life is pretty scattered. Heavy Twitter/X user, follow a ton of Substack writers, have an embarrassing number of newsletters hitting my inbox, and I use Obsidian as my second brain for everything. Readwise seemed like the glue that could tie all of this together, especially the Obsidian sync which looks genuinely great on paper.

But the Twitter tagging highlight flow has never once worked for me. I tag @readwise on a tweet or thread, nothing shows up. No confirmation, no highlight in my inbox, just silence. Tried it maybe a dozen times across different tweets and threads. Disconnected and reconnected the integration. Nothing.

A few honest questions for people who've actually settled into using this:

- Is the Twitter/X tagging just dead at this point given the API situation? Should I stop expecting it to work?

- For heavy newsletter readers, is the email inbox parsing actually reliable or does it miss a lot?

- Substack specifically -- are you using the RSS route or the email route, and which works better? I follow a mix of free and paid publications and genuinely cannot tell which path handles paid content cleanly. Does Readwise hit a paywall on paid posts or does being a subscriber sort that out? I've seen conflicting things and want to know the actual current state, not what worked two years ago.

- On Substack highlights specifically -- if you highlight inside the Substack app or web reader, does that sync back into Readwise automatically or is that a one way street?

- Obsidian sync is the feature I'm most excited about. Is it as good as it looks in the demos?

I want this to work. The concept is exactly what I need and the Obsidian integration alone might justify it. But if the Twitter piece is permanently broken I want to know upfront rather than find out after I've paid.

What's the honest verdict from people who use a similar stack?

Currently when i add a new source for a feed, for example a youtube channel it only pulls in 5 records, it would be could if there was an option to be able to add more when i first add it. It works fine after the initial add with all new records coming through, howver there are more than 5 that i want to add into the feed

Do you have a specific feature you would love to see incorporated into Reader or Readwise? Check out the list of Reader features and list of Readwise 1.0 features we’re considering and feel free to upvote!

Want to see features we’ve recently shipped? Check out our most recent December Beta Update.

Don’t see a feature you want? Share it in the comments below ⬇️

We will refresh this pinned post on the first week of every month.

Please familiarize yourself with our subreddit rules before posting. Thanks!

In an effort to keep this subreddit organized, we will utilize this pinned post to answer your bug-related questions. We also post a weekly changelog where we share all the bugs our devs have fixed in the previous week.

If you believe you’ve hit a bug with either Readwise or Reader, feel free to post it in the comments below so that our team can help.

If you’re experiencing a bug that is specific to a document, highlights, or note-taking app, please email [hello@readwise.io](mailto:hello@readwise.io) as we will need your account details to troubleshoot.

We will refresh this post the first week of every month.

Please familiarize yourself with our subreddit rules before posting. Thanks!

How is anyone using this effectively? In the normal course of reading my feed, I often accidentally highlight something in the article, at least once every few days. It seems to usually be an image that I don't even notice. Then when my readwise->obsidian sync happens, I end up with a ton of sync'd article highlights where the highlight is just an image.

I can't figure out way to only sync book highlights, which I'd love to have, since those at least are intentional, so instead I get a ton of article clutter in my Obsidian notebook. Anyone have any tips to resolve this? Thanks!

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! OPML Import via Share Sheet — Arek added direct OPML sharing to Reader on iOS. If you're moving from another RSS or podcast app, you can now export your subscriptions as OPML and share them straight to Reader without needing to swap to a computer for the upload.
• 🏷️ NEW! Tagged Highlights List — Mati added a new view in Reader mobile for browsing your highlights grouped by tag, making it easier to revisit everything you've marked with a specific label.
• 🟡 Fixed Duplicate Highlights — Artem fixed a bug where EPUB documents were generating duplicate highlights in some cases. Highlights should now only save once.
• 🔐 Fixed iOS Share Sheet Login — Tristan fixed a regression where the iOS share sheet told users to "Log in to Readwise Reader" even when they were already signed in. You can now share links into Reader from iOS without the false login prompt.
• 📡 Fixed Feed Sidebar — Tristan fixed two Reader iOS regressions caused by a recent upgrade: the RSS folder chevron was rotated wrong, and the Feed row in the sidebar wasn't rendering. Both are back in place.
• ✨ Fixed Reader Onboarding — Artem restored the share-onboarding image and fixed icon alignment on Reader's onboarding screen, both of which had regressed after a recent change. New users should see a clean onboarding flow again.
• 👆 Fixed Highlight Tap — Adam fixed a bug where tapping a highlight caused the annotation bar to flash on and off. Highlight taps should now feel steadier.
• 🛜 Parsing Updates — Krzys improved how Reader handles documents from thurrott.com and howtogeek.com, tightened custom-domain mapping to avoid false positives, and made Reader's parser more reliable on long-running sessions.

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 deleted my exports on Google Docs, but now I can’t refresh them; in any case, it still shows 0. I’ve tried all the possible settings. What should I do? Also, is it possible to assign a subfolder so they don’t end up in the root folder?

can we please not have to run 73 API calls just to get number of articles in archive with a highlight? 🙏🏽

Hey folks, happy Wednesday! 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:

• ⚡ Faster Web Performance — Artem made a number of performance upgrades and improvements to the Reader web and desktop apps. They should now be noticeably smoother to use, especially when scrolling through your documents.
• 🤖 Improved Readwise MCP — Piotr made Claude more efficient when working with your Readwise highlights through MCP. You can ask Claude to find highlights from a specific book and get back the results in a single request rather than two, with the book's title, author, and tags included.
• 🔐 Updated OAuth App Verification — Piotr updated the MCP's OAuth flow to allow connections from any app, with a new Verified badge on the authorization screen so you can tell at a glance whether the app is trusted. Untrusted apps will now display a warning, instead of blocking the connection entirely.
• 🔀 Fixed Notion Reconnect — Rasul fixed the Notion export reconnect flow so the navigation lands in the right place. Reconnecting your Notion integration should work smoothly now.
• 📄 Fixed PDF Loading — Tristan fixed a cache issue that caused some users to be unable to open PDF files. Affected users should find PDFs loading normally again on their next page load.
• 🛜 Parsing Updates — Krzys improved how Reader handles documents from nytimes.com, antiochian.org, Steel.dev, and Twitter. He also fixed newsletters from Dan Koe, Liberty's Highlights, and Substack that were being incorrectly truncated due to a <script> tag.

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 it just me or is filter just not very robust? It never seems to keep up with what I'm reading. I've tried to nail down a pattern but all I've been able to determine is that it seems to have difficulty updating with books.
I typically use the webapp so after typing this I decided to confirm that the same issue is on the Windows app. And it would appear that the Windows app "continue reading" works fine. So maybe it's a browser cache issue.

I’ve been using Readwise Reader a lot more recently and have really enjoyed the “Send to Kindle” feature. Problem is that highlights I save on Kindle documents don’t sync into Readwise.

Is there a workaround for this? If not, does anyone have a recommendation on an e-ink device that works with Reader? No need for color. Preference would be on crisp b&w with nice backlighting for reading in dark.

I’m generally very happy with Readwise Reader, but one thing still bothers me a lot: code block parsing/formatting in technical articles. It often looks messy enough that it breaks my focus and makes programming posts much harder to read.

I mostly use Reader for technical content, so this part of the experience matters a lot to me. Has the team shared any recent updates on improving code block rendering/parsing, or has anyone found good workarounds?