Skip to content


The dataview query language is a simple, structured, custom query language for quickly creating views on your data. It supports:

  • Fetching pages associated with tags, folders, links, and so on.
  • Filtering pages / data by simple operations on fields, like comparison, existence checks, and so on.
  • Sorting results based on fields.

The query language supports the following view types, described below:

  1. TABLE: The traditional view type; one row per data point, with several columns of field data.
  2. LIST: A list of pages which match the query. You can output a single associated value for each page.
  3. TASK: A list of tasks whose pages match the given query.

General Format

The general format for queries is:

TABLE|LIST|TASK <field> [AS "Column Name"], <field>, ..., <field> FROM <source>
WHERE <expression>
SORT <expression> [ASC/DESC]
... other data commands

Only the table/list/task statement is required - if the "from" statement is omitted, the query runs for all files in your vault. You can specify data commands like WHERE multiple times; they will simply run in the order they are written.

Query Types

List Queries

Lists are the simplest view, and simply render a list of pages (or custom fields) which match the query. To obtain a list of pages matching the query, simply use:

LIST FROM <source>
LIST FROM #games/mobas OR #games/crpg

You can render a single computed value in addition to each matching file, by adding an expression after LIST:

LIST <expression> FROM <source>
LIST "File Path: " + file.path FROM "4. Archive"
  • 2020-12-18 DN: File path: 4. Archive/Daily Notes/2020-12-18
  • 2020-12-16 DN: File path: 4. Archive/Daily Notes/2020-12-16
  • 2020-12-17 DN: File path: 4. Archive/Daily Notes/2020-12-17
  • 2020-12-15 DN: File path: 4. Archive/Daily Notes/2020-12-15

If you don't want the file name / group key included in the list view, you can use LIST WITHOUT ID:

LIST WITHOUT ID <expression> FROM <source>
LIST WITHOUT ID file.path FROM "4. Archive"
    1. Archive/Daily Notes/2020-12-18
    1. Archive/Daily Notes/2020-12-16
    1. Archive/Daily Notes/2020-12-17
    1. Archive/Daily Notes/2020-12-15

Table Queries

Tables support tabular views of page data. You construct a table by giving a comma separated list of the YAML frontmatter fields you want to render, as so:

TABLE, file.mtime FROM <source>

You can choose a heading name to render computed fields by using the AS syntax:

TABLE (file.mtime + dur(1 day)) AS next_mtime, ... FROM <source>

An example table query:

  time-played AS "Time Played",
  length AS "Length",
  rating AS "Rating"
FROM #game
SORT rating DESC
File Time Played Length Rating
Outer Wilds November 19th - 21st, 2020 15h 9.5
Minecraft All the time. 2000h 9.5
Pillars of Eternity 2 August - October 2019 100h 9

If you don't want the default "File" or "Group" field in your output (either to replace it or because it is unneeded), you can use TABLE WITHOUT ID:

  time-played AS "Time Played",
  length AS "Length",
  rating AS "Rating"
FROM #game
SORT rating DESC
Time Played Length Rating
November 19th - 21st, 2020 15h 9.5
All the time. 2000h 9.5
August - October 2019 100h 9

Task Queries

Task views render all tasks whose pages match the given predicate.

TASK FROM <source>
TASK FROM "dataview"
  • I am a task.
  • I am another task.
  • I could be a task, though who knows.
    • Determine if this is a task.
  • I'm a finished task.

You can filter (WHERE), group (GROUP BY), sort (SORT) tasks in these queries as desired using typical dataview statements:

TASK FROM <source>
WHERE <predicate>
TASK FROM "dataview"
WHERE !completed
GROUP BY file.folder

Folder 1

  • I am a task.
  • I am another task.
  • I am yet another task in another file in the same folder.

Folder 2

  • I could be a task, though who knows.

Folder 3

  • What even is a task, anyway?

A common use case for tasks is to group them by their originating file:

TASK FROM <source>
TASK FROM "dataview"

dataview/Project A

  • I am a task.
  • I am another task.

dataview/Project A

  • I could be a task, though who knows.
    • Determine if this is a task.
  • I'm a finished task.

Calendar Queries

Calendar views render all pages which match the query in a calendar view, using the given date expression to chose which date to render a page on.

FROM <source>
CALENDAR file.mtime
FROM "dataview"

The output will be a calendar that displays a dot per file in the dataview directory. The dot will be placed on the date that the file was modified on.

Data Commands

The different commands that dataview queries can be made up of. Commands are executed in order, and you can have duplicate commands (so multiple WHERE blocks or multiple GROUP BY blocks, for example).


The FROM statement determines what pages will initially be collected and passed onto the other commands for further filtering. You can select from any source, which currently means by folder, by tag, or by incoming/outgoing links.

  • Tags: To select from a tag (and all its subtags), use FROM #tag.
  • Folders: To select from a folder (and all its subfolders), use FROM "folder".
  • Single Files: To select from a single file, use FROM "path/to/file".
  • Links: You can either select links TO a file, or all links FROM a file.
  • To obtain all pages which link TO [[note]], use FROM [[note]].
  • To obtain all pages which link FROM [[note]] (i.e., all the links in that file), use FROM outgoing([[note]]).

You can compose these filters in order to get more advanced sources using and and or.

  • For example, #tag and "folder" will return all pages in folder and with #tag.
  • [[Food]] or [[Exercise]] will give any pages which link to [[Food]] OR [[Exercise]].

You can also "negate" sources to obtain anything that does NOT match a source using -:

  • -#tag will exclude files which have the given tag.
  • #tag and -"folder" will only include files tagged #tag which are NOT in "folder".


Filter pages on fields. Only pages where the clause evaluates to true will be yielded.

WHERE <clause>
  1. Obtain all files which were modified in the last 24 hours:

    LIST WHERE file.mtime >= date(today) - dur(1 day)
  2. Find all projects which are not marked complete and are more than a month old:

    LIST FROM #projects
    WHERE !completed AND file.ctime <= date(today) - dur(1 month)


Sorts all results by one or more fields.


You can also give multiple fields to sort by. Sorting will be done based on the first field. Then, if a tie occurs, the second field will be used to sort the tied fields. If there is still a tie, the third sort will resolve it, and so on.



Group all results on a field. Yields one row per unique field value, which has 2 properties: one corresponding to the field being grouped on, and a rows array field which contains all of the pages that matched.

GROUP BY field
GROUP BY (computed_field) AS name

In order to make working with the rows array easier, Dataview supports field "swizzling". If you want the field test from every object in the rows array, then rows.test will automatically fetch the test field from every object in rows, yielding a new array. You can then apply aggregation operators like sum() over the resulting array.


Flatten an array in every row, yielding one result row per entry in the array.

FLATTEN (computed_field) AS name

For example, flatten the authors field in each literature note to give one row per author:

TABLE authors FROM #LiteratureNote
FLATTEN authors
File authors
stegEnvironmentalPsychologyIntroduction2018 SN Steg, L.
stegEnvironmentalPsychologyIntroduction2018 SN Van den Berg, A. E.
stegEnvironmentalPsychologyIntroduction2018 SN De Groot, J. I. M.
Soap Dragons SN Robert Lamb
Soap Dragons SN Joe McCormick
smithPainAssaultSelf2007 SN Jonathan A. Smith
smithPainAssaultSelf2007 SN Mike Osborn

A good use of this would be when there is a deeply nested list that you want to use more easily. For example, file.lists or file.tasks. Note the simpler query though the end results are slightly different (grouped vs non-grouped). You can use a GROUP BY to achieve identical results but would need to use rows.T.text as described earlier.

table T.text as "Task Text"
from "Scratchpad"
flatten file.tasks as T
where T.text
table filter(file.tasks.text, (t) => t) as "Task Text"
from "Scratchpad"
where file.tasks.text

FLATTEN makes it easier to operate on nested lists since you can then use simpler where conditions on them as opposed to using functions like map() or filter().


Restrict the results to at most N values.


Commands are processed in the order they are written, so the following sorts the results after they have already been limited: