Types you define, files you can read
Eighteen field kinds — text, number, date, select, currency, markdown, relations, computed. Each type gets its own file extension, so a record is just `roadmap.project` on your disk.
Define your own object types, then see them as tables, boards, calendars, timelines and printable pages. Everything lives as plain JSON and Markdown in a folder you own — no account, no server, nothing to lock you in.
Your records are files in a folder you already own. tabls is the good way to shape them, look at them, and print them — and it never becomes the thing standing between you and your data.
Eighteen field kinds — text, number, date, select, currency, markdown, relations, computed. Each type gets its own file extension, so a record is just `roadmap.project` on your disk.
Grid, board, calendar, gantt, tree, chart, map, graph, photo grid, cards, forms, dashboards. All over the same records, and the views are files too.
There is no tabls server, so anything that syncs a folder makes it multi-user: git, OneDrive, Dropbox, Google Drive, a network share. Your data, your infrastructure, your rules.
Records are small text files, so a diff reads like a sentence and a merge is an ordinary text merge. The file tree marks what is modified, added, untracked or conflicted.
No account, no cloud, no telemetry. The app makes exactly one network request — the update check — and Settings can switch that off too.
Compose a page from blocks, pick the paper and margins, set headers and footers with page numbers, and print or PDF it. Page breaks where you put them.
Open any folder on your disk. tabls indexes what is already in it — JSON, Markdown, PDFs, images — and leaves every file exactly where it is.
Add a type, give it fields, add records. Each record is written as a plain file, named after its title, with your type as its extension.
Add views over the same records — grid, board, calendar, a page laid out for A4. Then sync the folder however your team already does.
A desktop workspace over a folder on your disk. You define your own object types — the fields your work actually has — and then look at them as tables, boards, calendars, timelines, graphs or pages laid out for print. The records themselves stay plain JSON and Markdown files.
In the folder you picked, in files you can open in any editor. tabls builds an index to query them quickly, but that index is a disposable cache — delete it and it is rebuilt from the files. Nothing is uploaded anywhere, and there is no database only tabls can read.
Fields are typed — dates are dates, currency is currency, a relation points at another record. Records link to each other and you can see the links as a graph. And because each record is its own file, your version history and your backups are the ones you already have.
Yes — you bring the sync layer. A vault is a folder, so git, OneDrive, Dropbox, Google Drive or a plain network share all work, and you keep control of where the data sits. Different records never collide, because they are different files. What tabls does not do is realtime: there are no live cursors and no field-by-field merging, so two people editing the same record at the same moment is settled by whatever syncs the folder — git merges the text, OneDrive keeps a conflict copy. The file tree shows you what changed either way.
Windows 10 and 11 today, as a signed installer that keeps itself up to date. There is no macOS or Linux build yet.
The builds you can download today are free, and there is no account to create. tabls is in active development, and pricing beyond that is not settled yet.
The app updates itself, so this is only for the bigger news — new view types, a macOS build, that kind of thing. No spam.
Only about tabls releases. Nothing else, ever.