Bases View Extract copies a saved view into your note

Name: Bases View Extract
Author: theluckystrike

Copy a saved Bases view into a note.

Install in Obsidian

Directory page Source on GitHub

MIT · no telemetry · core features free

The extraction window selects Active projects from a Base with two views. — Open larger

version: 1.2.0
released: 2026-10-21
downloads: 28
review: Passed
health: Excellent
license: MIT
listed for: Desktop, Mobile
obsidian: 1.13.4 or later

Desktop app tests do not prove phone or tablet behavior. Live GitHub sign-in and payment were not tested.

Directory facts fetched 2026-10-23 07:28 UTC from community.obsidian.md/users/theluckystrike.

About Bases View Extract

You reuse one view from a larger Base in a project note, weekly review or dashboard.

Bases View Extract copies one named view from a Base into a complete embedded query. Shared definitions stay with the view. Check the YAML preview, then insert the block at your selection without changing the source Base.

Choose a saved view, check its YAML and insert it in a weekly review

Free features

Choose a named view

Select a Base file and a saved view by name. The output keeps that view and leaves the others out. Names are case-sensitive, and a duplicate selected name stops extraction.

Keep shared definitions

Keep shared filters, formulas, property labels and summary definitions with the selected view. Unknown top fields and view options remain as parsed values. A community view still needs its provider.

The preview retains shared filters, a formula and summary definitions. — Open larger

Preview the complete query

Read the fenced query before insertion, including sort rules, group setup and summary choices. Group order retains its sequence and null keys. YAML comments and original spacing do not survive serialization.

The query preview retains group order with a null entry. — Open larger

Copy to clipboard

Copy the complete fenced query and its shared definitions for another note or template. The editor and source stay unchanged, and one saved view is free. If clipboard access fails, select the preview text and copy it manually.

The extraction preview stays open after copying a saved view query. — Open larger

Check note context

The preview explains that the target note supplies the query context. Expressions with this, wikilinks, link or file calls, or parent paths trigger a stronger warning. The check is conservative; review your expressions before insertion.

A warning appears for expressions that may change in the target note. — Open larger

Pro features

Pro costs $5 a month or $15 one time through GitHub Sponsors. One sponsorship turns on Pro in every plugin that has it.

Separate sections for several views Pro

Select several views to create separate note sections in source order. Each section has a heading and a complete query with shared definitions. Check the combined preview before inserting it.

Two selected views appear as separate sections in the combined preview. — Open larger

Named query presets Pro

Save a named snapshot of the source query and chosen views. Source edits do not update it, and duplicate preset names are rejected. Delete preset removes the local copy even with Pro off.

A Weekly review preset appears in the local saved snapshot list. — Open larger

See how Pro works

Set up Bases View Extract

needs

Obsidian 1.13.4 or later
The core plugin Bases, turned on

steps

Open the target Markdown note and place the cursor on an empty line, or select text to replace.
Run Extract a saved view from the command palette.
Select a Base file and its named view.
Read the preview and context notice, then choose Copy to clipboard or Insert at selection.

If the app can't find a new plugin yet, try again later. Obsidian says a plugin that passes the review shows in the app within 24 hours.

How to copy a saved Bases view into a note

Known limits of Bases View Extract

Extracted queries and saved presets are snapshots and do not update from source edits.
YAML parsing and serialization remove comments and change original spacing.
The target note supplies query context, so expressions can select different notes after extraction.
Extraction retains unused shared formulas without calculating results or analyzing dependencies.
Community view types still need their provider to render the extracted query.
Insertion supports one editor selection and stops if the target note, text or selection changes.
Physical mobile devices, third-party view providers and results across different note contexts were not tested.

Questions about Bases View Extract

Does an extracted block update with the source?

The inserted block is a snapshot without a connection back to the source. Run extraction again after a source edit to get a new copy.

Does it keep only formulas used by the view?

No, unused shared formulas remain present. Extraction keeps parsed definitions without evaluating filters or calculating results.

What if I edit the target during the preview?

Insertion stops if the target note, text or selection changes. Close the window and run the command again.

Where do query presets stay?

Presets stay in the plugin’s data.json in your vault. Vault sync can copy that file to other devices.

Does clipboard copy include the result rows?

No, it copies the query source with its base fence. Check expressions in the note where you paste it, because that note supplies the context.

Network use

Before GitHub sign-in, the plugin sends nothing; sign-in sends a public client ID and read:user to github.com, then polls for authorization. api.github.com receives an authenticated query for your account, sponsorship tier and total payment; no note content, file names or vault data leaves. Successful checks last 7 days; failed checks retry after 6 hours, and Refresh requests an earlier check.

Read the full network disclosure

Questions or ideas?

Tell me what is broken in Bases View Extract, or what it should do next.

Send feedback

Bases View Extract 1.2.0, MIT license