Database views
Database views over plain Markdown notes.
Give your notes properties, then see them as a table, board, or calendar — structured workflows without leaving plain Markdown behind.
14-day free trial, no card required. macOS, Windows, and Linux.
Properties are first-class
Add YAML frontmatter to a note and those properties become typed, first-class metadata — a status, a due date, a priority, a project, whatever your work needs. Because the properties live in the Markdown itself, you keep full ownership and portability; there’s no separate database you can’t export.
One set of notes, several views
Save a filter over your notes as a database view and render the same notes the way the task calls for:
- Table — scan and sort properties across many notes at once
- Board — a kanban board grouped by a property like status
- Calendar — place notes on the days their date property points to
Structure that stays yours
Views are saved filters, not a new storage format — your notes remain Markdown on your device, exportable at any time. Pair views with wiki-links, backlinks, and full-text search and you get the structure of a database with the durability of plain text.
Frequently asked questions
- What are database views in NoteLace?
- Saved filters over your notes that render as a table, board (kanban), or calendar. They’re driven by note properties (YAML frontmatter), so the same notes can be viewed several ways.
- Do views change how my notes are stored?
- No. Views are saved filters; your notes stay as plain Markdown with YAML frontmatter and can be exported to .md at any time.
- What can I group or sort by?
- Any property you put in a note’s frontmatter — status, date, priority, project, and so on — across table, board, and calendar layouts.
- Are views per-workspace?
- Yes. Each workspace has its own notebooks, notes, tags, and views, so work and personal contexts stay separate.
Keep exploring
Add structure without giving up plain files.
Start your 14-day free trial. No card required.