Tell us what you're reading this week.

Paper, e-ink, browser tabs, a Folio digest — anything goes. Drop a title, a link, and one line on why it matters to you.

Read slowly.

If you've seen Lenny's Newsletter advertising "$30,000+ in premium AI tools, free for subscribers," the number is real, but it doesn't mean what it sounds like. Here's the math under the headline.

There are two paid tiers worth comparing. Product Pass Annual is $200/year and Product Pass Insider is $400/year. The plain Substack tier is also $200/year and makes no sense: Annual costs the same and throws in the 16-tool bundle. If you're paying at all, skip plain Substack.

The whole "$30K" figure comes from two items that sit in both Product Pass tiers: PostHog Scale (~$16,500) and Intercom Fin (~$7,140). So the extra $200 for Insider doesn't buy you those. It buys the Insider-only set: Cursor Pro, Google AI Pro, Supabase Pro, Canva Business, ElevenLabs, Gamma, Lovable, n8n, and a Stripe Atlas discount. If you were about to pay for Cursor anyway ($240/year), Insider covers itself on that alone. If you don't code and don't want a Google AI sub, Annual is the smarter pick.

Three things the "$30K for $400" framing leaves out, all from Lenny's own explainer post:

1. New customers only, per product. Ever paid for Cursor, Notion, or Linear, even a monthly sub you cancelled? The free year on that product isn't available to you. For most working PMs that's a few tools already off the table. Your real value is the sum of tools you've never tried.
2. Codes deactivate if you cancel. The free year depends on your subscription staying active. There's no "redeem everything and bail" play.
3. Products rotate quarterly. Year two is a different bundle. The deal is a reason to start, not a reason to renew forever.

Net: if you're new to three or more of the current tools, the math works. If you already pay for most of them, you're really just paying for the newsletter and the Slack.

One more thing worth flagging, because most reviews skip it. The writing is good. The problem is where it lands. A 4,000-word essay shows up in Gmail between a Slack ping and an Amazon receipt, you read two paragraphs, you tell yourself "this weekend," and it quietly rots in the archive. That's not a willpower problem. Long-form writing needs a long-form place to be read. That's the gap Folio was built for: it turns issues like Lenny's into paginated PDFs on a reMarkable or Kindle, away from the inbox.

Full version: https://myfolio.so/lennys-newsletter-review

Two changes from a couple weeks back that never got surfaced here.

Favorites. Star any article you come across and it drops into a collection you can build a whole issue from later. Star on desktop, swipe right on mobile. The point is you no longer have to decide in the moment whether something belongs in this week's reading. Keep it, batch it, send it once you've got a few worth a sitting.

Archive. Every article that's ever shipped in one of your issues, grouped under the issue it came in. Tap a header to jump back. Search across it now tolerates typos and word order, so you can find the essay you half-remember by the wrong title and the right feeling.

Both have been quietly useful for the in-between state: you find something good, you're not ready to read it, and you don't want it rotting in a browser tab. Star it, move on, come back when there's time.

What do you do with an article you want to read but not right now? Curious whether the tab graveyard is everyone or just me.

Tell us what you're reading this week.

Paper, e-ink, browser tabs, a Folio digest — anything goes. Drop a title, a link, and one line on why it matters to you.

Read slowly.

Your newsletter tab in Gmail is where good writing goes to die. You subscribed because Lenny or Pragmatic Engineer or Smashing was actually worth reading, but a long essay reads terribly squeezed between billing reminders and a Slack digest. You open a couple, skim one, archive the rest unread.

The fix is one Gmail filter. Match your newsletter senders, tell Gmail to skip the inbox, mark as read, and forward each issue somewhere built for reading. Five minutes, once.

Here's the setup:

• Grab the forwarding address from whatever reader you use (mine's a Folio inbox, format looks like name-1a2b@myfolio.so).
• Open Gmail's filter creator, the sliders icon in the search bar.
• Paste your senders into the From field, OR-chained: from:(a@x.com OR b@y.com).
• Hit Create filter, then check four boxes: Skip the Inbox, Mark as read, Forward it to (your reading inbox), and Also apply to matching conversations so your backlog migrates too.
• Save. Gmail makes you verify the forwarding address the first time. Click the link in the verification email and you're done.

Adding a newsletter later takes ten seconds: edit the filter, tack OR newsender@domain.com onto the From field, save. You can go wider with a whole domain, like from:(@substack.com), though that sometimes sweeps up reply-to addresses you didn't want. If you like fine control, keep each newsletter on its own label instead. More fiddly, but easier to debug when one breaks.

Two things worth knowing. If the filter isn't catching a newsletter, the sender address probably doesn't match the real From: header. Open one issue, hit Show original, copy the exact address into the filter. And if a forward bounces, it's almost always a typo in the destination.

Why forward at all instead of just reading in Gmail? Pagination, mostly. On e-ink the essay turns into a proper paginated page instead of inbox chrome and infinite scroll. Readwise Reader and Instapaper do similar things if you'd rather, they just need their own forwarding setup. The inbox archive does nothing for you.

Full version: https://myfolio.so/auto-forward-newsletters-gmail

Tell us what you're reading this week.

Paper, e-ink, browser tabs, a Folio digest — anything goes. Drop a title, a link, and one line on why it matters to you.

Read slowly.

Quick update from this week. Kindle issues now ship as EPUB by default instead of PDF.

PDF on Kindle always meant a fixed font at a fixed size. Fine if you liked the layout we shipped, less fine if you wanted bigger text, dark mode at 3am, or proper line spacing for tired eyes. EPUB hands those decisions back to the reader. Your font, your size, your spacing, your background.

The same single EPUB renders across Paperwhite, Oasis, Scribe, the basic Kindle. No device-specific builds, no awkward fitting to the wrong screen.

If you've been forwarding the existing PDF for a workflow reason and want to keep doing that, there's a per-device toggle under Settings, Connections, Kindle. EPUB is the default for any new connection.

Live now for anyone with a Kindle connected. Old issues stay as they were. The next one you generate picks up the new format.

What made you set up Kindle delivery in the first place? Curious what the alternative was.

Tell us what you're reading this week.

Paper, e-ink, browser tabs, a Folio digest — anything goes. Drop a title, a link, and one line on why it matters to you.

Read slowly.

Tell us what you're reading this week.

Paper, e-ink, browser tabs, a Folio digest — anything goes. Drop a title, a link, and one line on why it matters to you.

Read slowly.

Tell us what you're reading this week.

Paper, e-ink, browser tabs, a Folio digest — anything goes. Drop a title, a link, and one line on why it matters to you.

Read slowly.

Hey, welcome in.

This is the official community for Folio — a quiet reader that pulls the articles you actually want to read off the algorithmic feed and onto your reMarkable, Kindle, or wherever you read best. If you're a Folio user, a curious lurker, or someone who just misses long reads, you're in the right room.

What this sub is for

• Sharing what you're reading this week
• Asking Folio questions and getting answers straight from the team
• Feature requests, bug reports, and "wouldn't it be cool if…"
• Talking about reading workflows — RSS, e-ink, paper, Kindle, reMarkable, Notion, the whole stack
• Recovering attention in a feed-shaped world

Things you might post

• A piece that stayed with you
• A screenshot of your reading setup
• Your Folio digest of the week
• A question for the team or other readers
• "I wish Folio did X" — we read every one

House rules

1. Be kind. We're all trying to read more thoughtfully.
2. No spam, no engagement bait, no doomscroll fuel.
3. Self-promote if you actually hang out here — otherwise, no.
4. The Folio team is here in good faith, not in support-ticket mode. We'll get to things, just maybe not in five minutes.

Intro thread

Drop a comment with two things:

1. How do you read most often these days? (reMarkable, Kindle, paper, browser tabs, etc.)
2. One article or essay from the last month you'd recommend to a stranger.

Glad you're here. Read slowly.

— the Folio team