Obsidian Web Clipper Not Working? Fixes for Every Error

Obsidian Web Clipper is a great free extension, and most of the time it just works. When it doesn’t, the error is usually short and cryptic: “Unable to find a vault”, a note with only a title, a popup that stays blank.

The good news: almost every failure comes from one of a handful of causes. It helps to know how the clipper works. It extracts the page in your browser, copies the Markdown to your clipboard, then opens an obsidian:// link that tells the Obsidian app to create the note. So three things must line up: the browser extension, the clipboard, and the Obsidian app with the right vault.

Below, one section per symptom, with the cause and the fix. Setting names are the ones shown in the extension (Web Clipper Settings).

”Unable to find a vault for the URL” (vault not found)

This message comes from Obsidian, not from the extension. The clipper asked for a vault by name, and Obsidian has no vault with that exact name.

1. Open Web Clipper Settings → General → Vaults.
2. Type the vault name, exactly as it appears in Obsidian’s vault switcher, and press Enter. Not the folder path (/Users/you/Documents/Notes), only the name (Notes). Case and spaces matter.
3. Check each template too: the Vault field in a template overrides the default and may still point to an old name.
4. Open the vault in Obsidian at least once on this computer, so the app knows it exists.

Vaults on network drives or inside WSL on Windows are known edge cases (both are open issues on the GitHub repo). If yours lives there, test with a local vault first to confirm the setup works.

Nothing appears in Obsidian, or the note is empty

The note gets created with the right file name but no content, or nothing happens at all. Most of the time the content never made it through the clipboard.

1. Make sure the Obsidian app is installed and can be opened by your browser. The first time, your browser asks whether to open Obsidian links: allow it.
2. Check the Note location of your template. It’s the folder or path of the note, inside the vault.
3. Open the browser’s developer console on the popup to see the actual error.
4. Still empty? Turn on Legacy mode (Web Clipper Settings → General). It sends the content in the link itself instead of through the clipboard. The trade-off: very long pages can fail silently, because browsers and operating systems cap the length of a link.

On Linux, clipboard access is the usual culprit (Wayland, KDE window rules, Flatpak). The official troubleshooting page has per-setup instructions.

The clip has missing content, or “No content”

By default, the clipper uses Defuddle to keep only the main content of the page. On some layouts it’s too conservative and drops sections you wanted.

1. Select the text you want on the page before clipping, or press Cmd/Ctrl+A to select everything.
2. Use the Highlighter to mark exactly the parts to keep.
3. For a site you clip often, create a template with a trigger for its URL and pull the right part with a selector variable such as {{selectorHtml:article}}.

If you see “Unable to extract page content”, reload the page and try again: the extension couldn’t read it, which happens on browser pages (settings, the extension store) and on some pages that are still loading.

Images are missing

This one surprises people: by design, images stay linked to their original URLs. They are not downloaded into your vault. If the site goes down or blocks hotlinking, the images disappear from your note.

To keep them locally, open the note in Obsidian and run the command Download attachments for current file from the command palette. Some sites (lazy-loaded galleries, base64 images, WeChat articles) still have open bugs, so check the result on pages that matter.

”Failed to save file”

This error shows up when the final save step throws, either the “Add to Obsidian” hand-off or the Save file… option that downloads a .md file instead.

1. Update both the extension and the Obsidian app. Many save bugs were fixed in minor releases.
2. Try Save file… from the dropdown next to the main button. If that works, the problem is the hand-off to Obsidian (go back to the vault and clipboard steps above).
3. If the file download itself fails, check that your browser allows downloads from extensions and isn’t asking where to save each file.

”Failed to fetch” and Interpreter not working

“Failed to fetch” almost always means a network request was blocked, and in practice it’s usually the Interpreter, the optional AI feature that runs prompts on the page.

1. In Web Clipper Settings → Interpreter, check that Enable Interpreter is on and that the provider has a valid API key.
2. For a custom provider, the Base URL must be the chat completions endpoint, usually ending in /chat/completions.
3. With Ollama, start the server with the extension origins allowed, otherwise you get a 403: OLLAMA_ORIGINS=moz-extension://*,chrome-extension://*,safari-web-extension://* ollama serve
4. If Interpreter returns irrelevant answers on long pages, Ollama’s default context is small (2048 tokens). Raise num_ctx or narrow the context with a selector.

Web Clipper not working on iOS or Safari

On iPhone and iPad, the clipper is a Safari extension, and it is off until you enable it.

1. In Safari, tap the button on the left of the address bar → Manage Extensions, and turn on Obsidian Web Clipper.
2. In iOS Settings → Apps → Safari → Extensions, allow it on all websites.
3. In iOS Settings → Apps → Obsidian, set Paste from Other Apps to Allow. Without it, Obsidian can’t read what the clipper copied, and you get empty notes.

On Safari (Mac or iOS), if notes come out with the wrong content or only a title, a known workaround reported on GitHub is to enable Legacy mode. A blank popup usually clears after closing the tab and reopening Safari.

How to save to a specific folder

Not an error, but one of the most searched questions. Each template has a Note location field: type the folder path inside your vault (for example Clippings/Articles). You can also edit the folder in the popup before clicking Add to Obsidian. Make one template per destination and add triggers (URL patterns) so the right one is picked automatically.

When the clipper keeps failing: an alternative

If you’ve gone through all of this and clipping is still fragile on your setup (a vault on a synced or network drive, an iPhone that keeps losing permissions, sites that come out empty), it can help to have a second tool that doesn’t depend on the same chain.

Minibase is a Chrome extension that works differently: it doesn’t need the Obsidian app open or a vault connection. It sends the page to an AI that identifies the main content and returns clean, structured Markdown. You can download the .md file, or let the Minibase Vault app (Mac and Windows) write it to a local folder that you can open as an Obsidian vault or place inside your existing one.

Be aware of the difference in approach: Minibase condenses pages for reading and for AI tools like Claude, it’s not a pixel-perfect copy. It’s free for 20 saves a month without an account, and Minibase+ costs $5.99/month.

For a side-by-side test of both tools, see Obsidian Web Clipper vs Minibase, and for the wider field, the best Obsidian web clippers in 2026. Many people keep both: the official clipper for quick captures into a template, Minibase for the pages that matter.