Obsidian users lack compact, scannable tables for small datasets
Some Obsidian users track short records such as lists of items with several attributes, but representing each record as a separate note can create thousands of tiny files. They want to work directly with CSV or JSON data in Bases, and one user is concerned Bases could become slow across a very large vault. Dense values can also be hard to scan without conditional colors.
For obsidian users managing compact structured datasets. Mentioned from Aug 2025 to Oct 2025 on product forums.
3 different people described this problem in 2 separate discussions.
- Indie fit
- 4.0/10
- Pain
- 6.0/10
- Frequency
- 5.0/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- Medium
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
This idea of backing Bases with CSV or Markdown tables is critical to me. I have lots of things I keep track of that are just a few words in each item. I just don’t use Obsidian for them at all, as I don’t want to have to have thousands of separate files with just a couple of words in each file
I would like to reiterate that my primary request is for the Bases feature to support working directly with CSV or JSON files
Build brief
See what to build and who will buy it
- 1 product idea with the smallest useful version and pricing
- 3 places to find your first customers
- 2 more quotes from people who have this problem
- Current workarounds, existing solutions and risks