---
site: steel.dev
collection: blog
canonical_url: https://steel.dev/blog/readwise
markdown_url: https://steel.dev/blog/readwise.md
content_signal: ai-input=yes, ai-train=yes, search=yes
related:
  - https://steel.dev/blog/more-browsers.md
  - https://steel.dev/blog/webrtc.md
  - https://steel.dev/blog/ship-browser-automation-to-users-with-steel-and-convex.md
title: Readwise's hardest sites go to Steel
description: When an article needs a real browser to load, Readwise hands it to Steel. That's more than 1.8 million sessions across 800+ sites so far.
date: 2026-11-18
authors: []
category: Customers
minutes: 3
entities:
  - Readwise
  - Steel
---

# Readwise's hardest sites go to Steel

When an article needs a real browser to load, Readwise hands it to Steel. That's more than 1.8 million sessions across 800+ sites so far.

> "I cannot say that any other tool we use is as successful as Steel is."
>
> Krzys S, Readwise Parsing Engineer

Readwise helps users save articles, newsletters and PDFs, then brings their best highlights back every day.

- **1.8M+**: Browser sessions Readwise has run on Steel since January.
- **7x**: Growth in monthly sessions since January.
- **800+**: Sites Readwise reads articles from through Steel.
- **2x**: More domains on Steel than four weeks ago.

Readwise has grown into the reading app of choice for 100,000+ users, from engineers to authors. Users save the articles they're reading, and Readwise turns each one into a clean copy they can come back to later. Some of those pages are complex or slow to load, and for a long time Readwise handled them with Selenium on servers they ran in-house. When the team looked at rebuilding that setup for Playwright, they tried Steel instead. Today the most complex pages, the ones that need a full browser, go to Steel.

## Running Selenium in-house

Krzys S, Readwise's parsing engineer, works on getting saved pages downloaded and turned into clean articles. The Selenium setup ran on Readwise's own droplets, and by his account it had become "a bit outdated." It struggled with new kinds of content, and when a download failed, it was hard to tell why.

Playwright was the natural replacement. But moving to it meant building a new set of droplets and running both setups side by side for a while so downloads kept working through the change. Krzys calls it "a huge switch."

## Why Readwise chose Steel

Steel meant Readwise could move to Playwright without building new servers first.

> "And then we learned about Steel, which took this from us. There was no need to run droplets."
>
> Krzys S, Readwise Parsing Engineer

Readwise started with a minor part of their downloads and made sure the change wouldn't affect the user experience. Their existing Playwright scripts now run through Steel's Sessions API, so for the domains they've moved, there are no browser servers of their own to run. For Krzys, Steel is the "part of our parsing flow which is well handled, and I do not have to worry too much."

What Krzys liked from the start was the viewer. He can watch a session live or open a past one and see where a download went wrong, whether the page failed to open or the script couldn't grab the content.

*Steel's session viewer. Watch a session live, or replay a past one.*

> "That was a huge thing because in \[Selenium], it wasn't possible \[...] And in here, we have the access to the past sessions."
>
> Krzys S, Readwise Parsing Engineer

When an issue comes up, Krzys can usually debug it himself. When it's out of his reach, he posts in a shared Slack channel, and Steel replies the same day with what the issue is and how long it'll take to handle.

> "From my perspective \[...] I think it is one of the smoothest contacts with \[any of our] vendors."
>
> Krzys S, Readwise Parsing Engineer

## The pages that need a full browser

Readwise sends Steel the pages that are hardest to fetch: JavaScript-built sites and articles that take time to load. Fetched with a simple request, those pages can come back empty or half-loaded. Steel opens each one in a real browser and returns the full article, including on many of the sites Readwise users read every day.

For Notion, Readwise opens the page in Steel, uses Playwright to scroll so every element loads, waits a couple of seconds at the end, and then Krzys checks in the viewer whether the method did the job. Plugging a new domain into the Steel flow is now "very simple," he says.

*A Playwright script running in a Steel session.*

## Twice the domains in four weeks

Krzys adds two to five new domains to Readwise's flow every week, often after users find a new site and start saving from it heavily. When a new domain is hard to load, Steel is the most likely place it goes. While we spoke, he pulled up the file that defines the flow and compared it with a month earlier: Readwise now runs twice as many domains on Steel as they did four weeks ago.

He's sure Readwise will expand their use of Steel as more of those domains turn up. "That's obvious," he says.

If your team runs its own browsers for pages that need one, [talk to us](https://steel.dev/enterprise) about moving them to Steel.
