Notion Web Clipper not working: fixes by symptom

The clipper fails in four distinct ways and each has a different cause. Find your symptom below and work down the list — the fixes are ordered cheapest-first, and most are things you can do in under a minute.

For context on how common each failure is: across 202 public Chrome Web Store reviews rated three stars or lower, 53 describe the clipper having simply stopped working, 40 describe wrong or partial content, 25 hit a “go online” error, and 18 are about missing property prefill (measured Sept 2026). If your problem feels like a weird one-off, it probably isn't.

Symptom 1: it worked, now nothing happens

You click the icon and get a spinner that never resolves, a blank popup, or an instant failure. This is the most-reported pattern and it is nearly always a stale authentication state or a stale service worker, not a broken installation.

1. Reload the page first. The clipper injects a content script. On a tab that was open across a browser update or a long sleep, that script is gone. Pressing Ctrl+R fixes a surprising share of “dead clipper” reports.
2. Check you're still signed in. Open notion.so in another tab. If Notion asks you to log in, the clipper has no session either — that's your whole problem. Sign in, then reload the page you want to clip.
3. Wake the service worker. Go to chrome://extensions, enable Developer mode, find the clipper, and click Service worker (or the reload arrow on its card). Chrome aggressively terminates MV3 background workers, and a worker that failed to restart looks exactly like a dead extension.
4. Toggle the extension off and on. Same page, the switch on the card. Cheaper than reinstalling and clears most transient state.
5. Check for enterprise or profile conflicts. If you're in a managed Chrome profile, try the clip in a clean profile. Policy-blocked host permissions produce silent failures with no error text.
6. Reinstall last. It works more often than it should, but it also wipes your settings, so treat it as the final step rather than the first.

If the clipper works on example.com but not on one specific site, skip to symptom 2 — that's extraction, not auth.

Symptom 2: the wrong content gets saved

You get the headline and nothing else, a cookie banner, a sidebar, a “related articles” list, or half the article. The clipper runs a readability-style heuristic that picks the DOM subtree most likely to be the article. On modern pages — lazy-loaded bodies, consent overlays, framework-rendered content, paywall teasers — it picks wrong.

1. Let the page finish loading, then scroll to the bottom. Lazy-loaded article bodies literally do not exist in the DOM until you scroll past them. Clip after scrolling and you'll often get the whole thing.
2. Dismiss the consent banner before clipping. Overlays are frequently the highest-scoring text block on the page at load time.
3. Select the article text, then clip. Selection usually overrides heuristics. Click at the start of the first paragraph, shift-click at the end of the last, then clip. This is the single most effective fix in this section.
4. Try the site's print view or reader mode URL. Many publishers expose ?print=1 or an AMP variant with a far simpler DOM that extractors handle correctly.
5. Accept that tables and code won't survive. There's no setting for this. The official clipper has no dedicated table handling, so a <table> arrives as flattened text and a code block loses its language. If you clip documentation or data posts, this is a structural limit rather than a bug to fix.

Symptom 3: “Please go online to save to Notion”

The error implies you're offline. Usually you aren't — you can load the very page you're trying to clip. What the message actually means is “a network request to Notion failed,” and the clipper can't tell the difference between no connectivity and a request that was blocked, throttled or timed out.

1. Retry once. A transient 5xx or a timeout on a large clip often succeeds on the second attempt.
2. Check whether Notion itself is degraded. Load status.notion.so. API trouble surfaces in the clipper as this error long before you notice it in the app.
3. Look for a VPN, DNS filter or corporate proxy. Anything intercepting TLS to api.notion.com produces exactly this message. Disable the VPN and retry to confirm.
4. Try a smaller clip. Select two paragraphs and clip those. If the small clip succeeds and the full page doesn't, you're hitting a size or timeout limit, not a connectivity one — and no amount of reconnecting will help.
5. Disable other extensions temporarily. Ad blockers and privacy extensions with aggressive filter lists can block the API request. Test in an incognito window with only the clipper enabled.

Symptom 4: my database or page doesn't show up as a destination

Two different causes depending on which clipper you're using.

With the official clipper, destinations come from your account's access. If a page is missing, check you're in the right workspace (the switcher is in the clipper popup), and that you actually have edit access — read-only pages don't appear. Recently created databases sometimes need a Notion reload before they show.

With any third-party clipper using an integration token, the cause is almost always an unshared database. The token sees nothing by default. Open the database as a full page, click … → Connections → Connect to, and select your integration. Connecting a parent page does not always cascade to child databases, and connecting an embedded view of a database is not the same as connecting the database itself. See the integration token walkthrough for the full sequence.

Symptom 5: I can't set properties while clipping

This one has no fix, because it isn't a malfunction. The official clipper creates the page with a title and a URL and nothing else; tags, status and dates are a second trip into Notion afterwards. Eighteen of those low-star reviews are asking for a pre-save form, and it hasn't shipped. If this is your bottleneck, the only route is a clipper that reads your database schema and shows you the fields before saving.

When none of this helps

If you've worked through the list for your symptom and the clipper still fails, the useful next step is isolating whether the problem is the extension, the browser profile, or the site. Clip a plain Wikipedia article in a clean Chrome profile with all other extensions disabled. Success there means the problem is site-specific or profile-specific; failure means it's the extension or your Notion account state.

Footnote, since you may be here looking for a different tool: Clipwise is a Chrome extension built specifically around these failures — layered extraction that keeps tables and code blocks, a pre-save property form, and a local queue that retries a failed save instead of discarding the clip. Free for 20 clips a day. It's new, with four users and no reviews, so test it against your own problem pages rather than taking that on trust.

Related guides

• Clip to Notion offline — the “go online” error in depth
• Notion Web Clipper alternative — honest comparison
• How to save articles to Notion — setup from scratch