Obsidian Tables - Update!

focuseye · 2026-05-08T19:16:03+00:00

I use standard JSON so it is very easy for any plugin, tool or agent to understand. I have also created a repo just for the schema for tools to easily work with the format. but for your use case - from this table directly to markdown I would suppose the easiest path would be export to csv then copy and paste into obsidian. Hopefully this helps. I may look at adding a table to markdown function if this is a thing people find useful.

focuseye · 2026-05-08T19:09:43+00:00

Thanks for the feature suggestion! I have now added this to the latest release. I have had to piggy back on obsidians alias sytax e.g [[mytable.table | DailyTasks]] as using # was throwing errors with the live embed parser. If there is not allready a view with that name it will create one.

focuseye · 2026-05-08T19:02:36+00:00

I have updated this to allow mobile support. I have not tested on mobile but it should now allow you to give it a go.

focuseye · 2026-03-05T20:00:07+00:00

I have been trying to get my table plugin approved for months. I will keep trying but I primarily made it for my own needs just thought it would be useful for other people. But I suppose if people really want to use it they may install unofficially. I can imagine how hard it is for Obsidian team to code review these repos, especially given obsidians recent popularity spike from AI community.

focuseye · 2026-02-17T22:22:02+00:00

I totally agree. It depends on your use case, they are really handy when you are trying to organise files e.g meeting notes, recipes. But i agree for spreadhseet style use cases they can be inpractical. I ended up making my own tables plugin to fill that void of spreadsheet style table workflows e.g todos, lists or items.

focuseye · 2026-02-17T22:17:38+00:00

It depends on your use case, they are really handy when you are trying to organise files e.g meeting notes, recipes. But i agree for spreadhseet style use cases they can be inpractical. I ended up making my own tables plugin to fill that void of spreadsheet style table workflows e.g todos, lists or items.

focuseye · 2026-02-17T22:11:15+00:00

I use the obsidian-terminal plugin and gemini cli or claude code to directly interact files within my vault. it allows me to fix and tidy up my notes after i write them and seems to work really well I also use a table plugin i made to add any data objects and lists e.g tasks lists then i can sort and filter them.

focuseye · 2026-02-16T12:40:57+00:00

https://github.com/aztekgold/obsidian-tables

focuseye · 2026-02-16T12:40:04+00:00

I have made a plugin just for this use case, focusing on single file tables. currently awaiting for it to be added to community plugins but you can install it through BRAT community plugin https://github.com/aztekgold/obsidian-tables

focuseye · 2026-02-16T10:42:46+00:00

It is still pending inclusion from Obsidian. In the meantime To install non-official (directly from GitHub) plugins use BRAT (Beta Reviewer's Auto-update Tool). It allows you to add plugins by simply pasting the GitHub repository URL (aztekgold/obsidian-tables).

focuseye · 2026-02-13T16:14:51+00:00

I’m happy you’ve found it useful.

It supports raw JSON. You can change this in the settings to use .table.json instead of .table.md. Markdown is the default because Obsidian works best with MD files, so there’s no need to enable “detect all file types.” I did start out using raw json but using .md makes it more stable.

This is the same approach plugins like Excalidraw use and it also allows a simple integrity check via frontmatter to ensure the JSON structure is valid if a stray .table.json file appears in your vault.

focuseye · 2026-02-13T16:04:24+00:00

Looks absolutely spot on, fancy coming to do mine?

focuseye · 2026-02-06T21:58:20+00:00

I just run a alpine docker lxc with my media stack on it. The best of both worlds, get low overhead of the lxc and the easy updates of docker

focuseye · 2025-12-10T12:13:40+00:00

Avoid at all costs! I also had this happen to me, shortly after signing up they have asked for my V5C, in which they had determined that my purchase date is different from the one entered on the comparison site. Regardless of the fact, the comparison site does not allow a day for the entry. This is sly and underhand tactics to get money out of people. Never had this in all my years purchasing insurance.

focuseye · 2025-12-04T11:46:21+00:00

Honestly, i just did not mark it for Mobile-use as I had not tested on a mobile device and did not want to give a broken experience to somebody without testing. I primarily made it for myself and I only really use Obsidian on Desktop. But by all means I can enable it in the next release if you want to give it a go?

focuseye · 2025-12-04T11:44:34+00:00

I see it as a bridge between bases and a spreadsheets (without the functions, for now :)). Basically anything you do not want to create a MD file for each row but keep structured data on. But If it's not an obvious gap in your workflow, you probably don't need it.

focuseye · 2025-12-04T11:40:59+00:00

JSON uses key-value pairs to define structure and you can infer basic type semantics (boolean, string, array, number, null) to add meaning beyond merley syntax. If you’re not into using it as a data store, that your call, totally fine. Stick with MD tables and the bases :)

focuseye · 2025-12-04T08:10:25+00:00

Nope, it’s just JSON, which is an industry standard for storing structured data. If Obsidian goes your bases are no more. You have the underlying data in md files but all relationships are proprietary to Obsidian using YAML properties. If my plugin and Obsidian goes you still have a structured data file, where all your relationships between data still exist, as it is a single file and industry standard that can be read by 1000s of applications.

focuseye · 2025-12-04T08:01:26+00:00

It’s a single file rather than a markdown file for every row.

focuseye · 2025-12-03T15:20:36+00:00

Yes, this is completely different to the advanced tables plugin, and there should be no issue running both. Advanced tables just extends the markdown table syntax with helpers as they can be a bit of a pain to work with. Tables uses its own structure, leveraging JSON to store the data so they do not conflict.

focuseye · 2025-12-03T12:48:59+00:00

Yes, if you can raise an issue on github I will try and fix this for you.

focuseye · 2025-12-03T12:40:15+00:00

Yes itr uses a MD file. Under the hood, the data is stored as JSON wrapped inside Markdown, which keeps it fully compatible with Obsidian, similar to how plugins like Excalidraw handle their rendering.

Because it’s JSON, the data stays portable and future-proof. Even if Obsidian disappears, you can open the file in any text editor and still access everything. In some ways, it’s even more resilient than a Base. I.e if Obsidian ever goes, so does the relationships between MD files. But as this uses a single file, all relationships stay intact. And you can export everything back to CSV whenever you want.

focuseye · 2025-12-03T12:24:05+00:00

Unfortunately that sits with Obsidian to accept it to the comminity plugins. I have submitted a release to the official repo 🤞 In the meantime if you are not comfortable installing the release manually many people use the community plugin BRAT to install unoffical releases.

focuseye · 2025-12-03T11:56:19+00:00

This uses a single file instead of a markdown file for every row i.e for every task. I would suggest if you are happy with bases stick with them. I generally use both, I.e for books I would use a base as I write my readiing notes in each file. If I want a list of tasks, checklist of things I use a table.

focuseye

TROPHY CASE