obsidian-web-clipper

Obsidian Web Clipper Templates

Obsidian Web Clipper is a browser extension that saves web content to an Obsidian vault as Markdown notes. Templates define how pages are captured — what metadata to extract, how to format the note, and which sites to auto-match.

Templates are configured as JSON. Users can import/export individual templates or full settings backups. When generating templates, output valid JSON the user can import directly.

Single-page scope. A clip only sees the page it fired on — the DOM loaded in the active tab. The extension is not an agent; it can't crawl, follow links, or visit other URLs. Selector, schema, and interpreter variables all resolve against that one page. If a template needs data spread across multiple pages, it can't gather it in one clip — design around what's on the page being clipped.

Caution: full settings exports contain interpreter API keys in plaintext (interpreter_settings.providers[].apiKey). Never quote them; flag exports stored in version control.

Adapt to the user's vault conventions

Templates hold opinionated conventions for folder layout, frontmatter property names, category/tag conventions, and note body structure. Match the user's existing conventions rather than inventing.

Before drafting a template, understand:

• Vault-level docs (CLAUDE.md, AGENTS.md, READMEs)
• An existing templates folder, sample notes of the type being clipped, or a previously exported clipper settings file
• Any YAML property-sort configuration (Linter or similar)
• User preferences uncovered in discussion

When conventions aren't discoverable or if the user isn't sure what they want, tailor what you can and fall back to minimal vendor-neutral choices. Flag any assumptions you've made so the user can adjust before import.

If the vault has a property sort order, mirror that order in the template's properties array.

Template JSON Schema

{
  "schemaVersion": "0.1.0",
  "name": "Template Name",
  "behavior": "create",
  "noteNameFormat": "{{title}} - {{site}}",
  "noteContentFormat": "{{content}}",
  "vault": "VaultName",
  "path": "folder/subfolder",
  "context": "",
  "properties": [],
  "triggers": []
}