You clip a long article into Notion, switch over to read it later, and half of it is gone. No error, no warning — the page just stops partway through. If that’s happened to you, you’re not doing anything wrong, and you’re definitely not alone. It’s one of the most common complaints about the official Notion Web Clipper, and there’s a concrete technical reason behind it.
What’s actually going on
Notion builds every page out of “blocks” — each paragraph, heading, image, and list item is its own block. When something saves a page into Notion through Notion’s API, it sends those blocks in a single request, and Notion’s API accepts a maximum of 100 blocks per request. A long article — a deep tutorial, a research piece, a meaty blog post — can easily run well past 100 blocks once every paragraph and image is counted.
When a clipper sends the page in one shot and doesn’t account for that ceiling, everything past the limit simply doesn’t make it in. The clip looks like it worked. It just quietly arrives incomplete. That’s why the truncation is so frustrating: there’s no failure message to tell you the back half of your article is missing until you go looking for it.
How to tell if this is your problem
A few quick signs it’s the 100-block limit and not something else:
- The cut-off point is roughly consistent — the page tends to stop around the same depth regardless of which article you clip.
- Short pages clip perfectly; only long ones get chopped.
- The clip ends mid-section rather than at a natural boundary.
If your clips are failing entirely or saving the wrong part of the page (a sidebar instead of the article), that’s a different problem — usually the clipper grabbing the wrong content container — and worth its own look.
What you can try with the official clipper
A few workarounds that sometimes help, with honest caveats:
- Clip in sections. Highlight the first portion, clip it, then highlight the next portion into the same page. Tedious, but it gets the whole article in. This only works on clippers that support selection-only clipping.
- Use “Reader” or simplified view first. Stripping a page to its core text can lower the block count enough to squeak under the limit on borderline articles. It won’t save a genuinely long piece.
- Save the URL, not the content. If you mostly need findability later, clipping just the link and a few notes sidesteps the issue entirely — at the cost of not having the text offline.
These are patches, not fixes. The real fix is a clipper that respects the API limit instead of fighting it.
The actual fix: clip in chunks automatically
The clean solution is for the clipper to split a long article into batches of 100 blocks or fewer and send them across multiple API calls, appending each batch to the same page. Done right, you never see it happen — you click once, and the entire article lands, however long it is.
That’s the specific thing Clipsage was built to fix. It chunks long pages across multiple Notion API calls so nothing gets silently dropped, lets you edit tags and properties right in the popup, and even queues clips offline to sync when you reconnect. It’s free for your first ten clips a month, so you can test it on the exact article that’s been getting cut off and see the whole thing arrive.
Try it: clip the longest article that’s been failing you → Add Clipsage to Chrome