Dataview Query Builder
Create Obsidian Dataview queries with visual controls for fields, folders, tags, filters, sorting, and limits. Preview DQL and copy the code block.
Build a Dataview Query Visually
Choose a view type, add fields and sources, define filters, then copy clean DQL for your Obsidian note.
```dataview TABLE file.link AS "Project", status, due FROM "Projects" WHERE status != "archived" SORT due ASC ```
What This Obsidian Dataview Tool Helps You Build
Dataview is powerful, but its query syntax can feel hard to remember when you only need a quick table, list, or filtered view inside Obsidian. This visual DQL builder turns the most common options into clear controls, so you can choose a view type, select fields, define a source, add conditions, sort results, and copy the final code block into your note.
It is designed for everyday Obsidian workflows such as project dashboards, reading lists, meeting notes, task reviews, content indexes, and personal knowledge management systems. Instead of starting from a blank code block, you can configure the query step by step and see how each option changes the generated Dataview Query Language output.
The builder does not read your vault or send note data to a server. It simply generates text in the browser. That makes it useful for beginners learning DQL and for experienced users who want a faster way to draft reliable TABLE and LIST queries.
Common Dataview Query Patterns
Most Obsidian dashboards use the same building blocks: a result type, an optional source, one or more filters, a sort order, and sometimes a limit. These examples explain when each part is useful.
TABLE Queries for Note Dashboards
Use TABLE when you want a structured overview with columns such as file name, created time, folder, tags, or custom frontmatter fields. This is a good fit for project indexes, CRM-style note lists, content calendars, and research dashboards.
LIST Queries for Focused Indexes
Use LIST when the output should stay simple, such as all notes from a folder, files tagged with a topic, or a reading list ordered by update time. A list query is often easier to scan when you only need links.
WHERE, SORT, and LIMIT Controls
Add WHERE rules for fields like status, priority, due date, or custom metadata. Sorting helps the newest, oldest, highest priority, or recently edited notes appear first, while LIMIT keeps large vault results manageable.
Practical Tips for Reliable Dataview Results
A query can be syntactically valid and still show empty results if the vault data does not match the rules. Use these checks before assuming the DQL is broken.
Match Field Names Exactly
Dataview field names are sensitive to spelling and structure. If your notes use frontmatter like status, priority, due, or project, make sure the query uses the same name. Inline fields and frontmatter fields can both work, but inconsistent naming across notes often leads to empty tables.
Start with a Small Source
Begin with a folder or tag that you know contains matching notes. Once the result appears in Obsidian, add WHERE rules one at a time. This makes it easier to find whether the source, the field value, or the sort expression is responsible for an unexpected result.
Keep Query Output Readable
A useful dashboard is not always the most complex one. Prefer a few meaningful columns, clear aliases, and predictable sorting. LIMIT is helpful when a vault grows large, because it keeps the view fast to scan and prevents a dashboard note from becoming noisy.
Example Workflows You Can Create
Use these scenarios as starting points when deciding which fields, folders, tags, and filters to configure in the builder.
Project Dashboard
Create a TABLE view for notes inside a Projects folder, then show columns for status, owner, due date, and priority. Add a WHERE rule to hide archived work and sort by due date so the next commitment appears near the top. This pattern works well for weekly reviews because it turns scattered project notes into a single operational view.
Reading and Research Index
Use a LIST or TABLE query for notes tagged with reading, source, book, article, or research. Add fields such as author, topic, rating, or summary status if you track them in frontmatter. Sorting by modified time helps surface material you recently annotated, while filtering by topic can produce a focused bibliography for a writing project.
Meeting Notes Review
Build a TABLE query that looks inside a Meetings folder and includes columns for date, participants, project, and follow-up status. A WHERE condition can show only notes where follow-up is not complete. This keeps decisions and action items visible without requiring a separate task manager.
Content Planning Board
For writing, publishing, or video planning, create a TABLE query from a Content folder and display fields such as channel, stage, publish date, keyword, and owner. Filter out completed items, sort by publish date, and limit the output to the next few pieces so your planning note stays concise. This is especially useful when one vault contains drafts, outlines, published work, and reference material together, because the query can separate active production from the archive.
Why Use This Obsidian Query Tool?
Visual Query Controls
Stop wrestling with small DQL syntax mistakes. Build useful queries with an intuitive interface that keeps the structure readable.
Real-Time DQL Preview
See the generated Dataview Query Language code as you modify parameters. The preview helps you understand how each setting changes the final output.
Private Browser-Based Generation
Zero data collection. All query generation happens locally in your browser. Your vault data never leaves your device.
How to Use the Visual Query Builder
Select View Type
Choose TABLE for a column-based dashboard or LIST for a simpler index of matching notes.
Filter & Configure
Add WHERE clauses, define SOURCE folders, and set SORT order using the visual controls.
Copy & Implement
One-click copy the generated code block and paste it directly into your Obsidian note.