When the clipper broke
Notion Web Clipper saves only the title and URL
You clip an article, open it in Notion, and there is a title, a link, and nothing else. Or the page is empty entirely. This is the most common complaint about this extension, and the cause is in how it is built rather than in your setup, which is why the usual troubleshooting does not help.
Why the body never arrives
The extension does not send Notion the page you are looking at. It sends the address, and Notion then fetches that address itself, from its own servers, and renders whatever comes back.
That second fetch is a different visitor. It has none of your cookies, is not signed in to anything, and can be refused or served a stub. When it comes back empty, what remains is exactly what was sent in the first place: the title and the link.
So the pages where this happens are predictable. Anything behind a login, anything behind a paywall, anything that builds its text in the browser after loading, and anything that turns away automated requests. On those pages no amount of reinstalling changes the result, because your machine did its part correctly.
What people report, word for word
Chrome Web Store reviews, unedited. The same sentence recurs for years, which is what makes this a design consequence rather than an outage.
Webpage not saving - just URL and title.
Does not save a full page - only title and link to it.
Used to save page content but now I'm only getting empty pages.
It just trying to render targeted page, but not saving rendered current page. Something went wrong last month.
Source: Chrome Web Store reviews, collected 5 September 2026. The card shows 3.32 stars; the last hundred reviews average 2.70, and 52 % of them are one or two stars.
What to try, in order
The first step tells you within a minute whether anything else on this list can help.
- Open the same page in a private window, signed out. What you see there is roughly what Notion's server will see. If the article is missing there too, the clipper cannot get it and no setting will change that.
- If the page is public, wait and clip again. A single failed fetch on Notion's side does happen, and a retry sometimes lands.
- Check the destination. Clipping into a database whose template overwrites the page body will leave you with a title and a link even when the fetch succeeded.
- Make sure you are signed in to Notion in the same browser profile, and that the workspace you are clipping into is the one you are looking at.
- For pages behind your own login, do not use a clipper that fetches server-side at all. Use one that reads the tab you already have open, or paste the text by hand.
- Report the specific address to Notion. A store review is not a support channel and nobody is triaging it.
What this means in practice
A clipper that fetches the page server-side can only ever save what an anonymous visitor can see. That is a fixed ceiling, not a bug list. Documentation behind a company login, a subscription article, your own dashboard: none of it can be clipped this way, no matter how the extension improves.
It also explains the shape of the reviews. The complaint reads identically in 2022, 2024 and 2026, and the rating has never recovered: 3.32 on the card, 2.70 across the last hundred reviews.
Clipping what is on your screen instead
Clean Clipper reads the page from the tab you have open, at the moment you press the button. There is no second fetch, so there is nothing to be refused.
- Pages behind your own login clip normally, because it is your session doing the reading.
- Pages that build their text in the browser clip normally, because it reads the finished page, not the source.
- The body is converted on your machine: headings, lists, tables, footnotes and code with its language tag.
- When there really is no article on the page, it says so and writes nothing rather than saving the menu.
- The result is a
.mdfile on your disk, not a row in a hosted database. - The clip is never uploaded – it is written by your browser, not by a service.
The two designs, side by side
This is about where the page is read, which is the whole difference. Notion offers a database behind the clip; Clean Clipper offers a file.
| What happens | Notion Web Clipper | Clean Clipper |
|---|---|---|
| Who reads the page | Notion's server, separately | Your browser, the tab you are on |
| Pages behind your login | Title and link only | Clipped in full |
| Pages built in the browser | Often empty | Clipped in full |
| Where the clip lands | A Notion database | A `.md` file in your folder |
| If the fetch is refused | A note with no body | Not applicable: there is no fetch |
What you give up by switching
Notion is a database and this is not. If the clip has to land in a Notion workspace, keep the official extension and use the private-window test above to know in advance which pages will work.
- The Notion workspace itself: databases, properties, templates, relations and shared pages.
- Anything your team does with the clip after it lands. A file on your disk is yours alone.
- Sync and mobile access. There is no phone app.
- Automatic tagging and page properties filled in by a template.
- Import of what you have already clipped. This extension does not touch your existing notes.
If you want both
These two do not compete for the same job, and using both is a reasonable answer rather than a compromise.
- Keep the Notion clipper for public pages that should live in a shared workspace.
- Install Clean Clipper for everything behind a login, which is exactly the set the other one cannot reach.
- Point Clean Clipper at a folder you already sync or back up.
- When something has to end up in Notion but the fetch comes back empty, clip it to Markdown and paste the result in. Notion accepts pasted Markdown and keeps the structure.
- Use the private-window test before blaming either tool: it tells you in seconds which of the two can see the page.