CSV Rule Check finds column errors in your local tables

Check CSV values, types and duplicates before you use an export.

MIT · no telemetry · core features free

The results table lists duplicate identifiers, an invalid age and other column errors in a sample CSV.
Open larger
version
1.1.0
released
downloads
17
review
Passed
health
Excellent
license
MIT
listed for
Desktop, Mobile
obsidian
1.13.4 or later

Phone and tablet use, live GitHub sign-in and paid sponsorship were not tested in this build.

Directory facts fetched from community.obsidian.md/users/theluckystrike.

About CSV Rule Check

You keep CSV exports in your vault and need to check their column values before using or sharing them.

CSV Rule Check checks your CSV against a rule file beside it. You get logical row numbers, column names and failed rules. Write a Markdown report to keep the result.

Inspect CSV errors and review a fix previewPlay demo

Free features

Choose a CSV and adjacent rules

Choose a CSV already in your vault. For people.csv, put the rules in people.csv.schema.json beside it. Missing files, invalid JSON and unknown rule keys stop the check.

Check explicit column rules

Check required values, string, number and boolean types, allowed values and uniqueness. Comparisons preserve case and spaces. Number checks leave text such as 001 unchanged.

Read errors by logical row

Row 1 is the header, and quoted line breaks stay inside one logical record. Results show up to 500 errors and the total count. Duplicate headers stop the check.

Write a Markdown report

Write a snapshot of the last successful check beside the source CSV. Numbered report names avoid existing files. The report includes the source path, record count and displayed errors.

Fix previews, corrected CSV copies, saved rule sets and batch checks need Pro.

Pro features

Pro costs $5 a month or $15 one time through GitHub Sponsors. One sponsorship turns on Pro in every plugin that has it.

Preview trim and default fixes Pro

Add trim or string defaults to your rules, then preview before and after values. Trim runs before defaults. Write a separate CSV copy; a changed source stops that write.

Check chosen files with saved rules Pro

Save a copy of a checked schema under a new name. Choose that rule set and 1 to 20 CSV files for a batch. A file that cannot be checked stops the new batch.

Set up CSV Rule Check

needs

  • Obsidian 1.13.4 or later

steps

  1. Put the CSV and its adjacent JSON rule file in your vault.

  2. Run Choose CSV and check adjacent rules from the command palette.

  3. Select the CSV and inspect the results table.

  4. Correct the source in your CSV editor, then check again.

  5. Select Write report to save the last successful check.

If the app can't find a new plugin yet, try again later. Obsidian says a plugin that passes the review shows in the app within 24 hours.

How to check CSV column rules in Obsidian

Known limits of CSV Rule Check

  • CSV and schema files each have a 5 MiB limit and load into memory.
  • This version uses commas and does not infer rules or convert field types.
  • Results and reports include at most 500 stored errors per file, alongside the total error count.
  • Required checks accept spaces as a value, and comparisons keep case and spaces significant.
  • Fix previews change only trim and default values, so other rule errors can remain.
  • Phone and tablet use, vault sync conflicts and large-vault performance were not tested.

Need a change for your team? I build custom Obsidian plugins and features.

Questions about CSV Rule Check

Can the checker infer my column rules?

No, you write the rules in JSON. A clean result means those rules passed, rather than proving your business records are correct.

Do spaces count as a missing value?

The required rule checks for an empty field. Spaces count as a value, and case and spaces affect allowed-value and duplicate checks.

How much data can I check?

The CSV and rule file each have a 5 MiB limit. The checker reads complete files into memory and stores up to 500 errors per file.

Can a fix preview repair duplicates?

Trim and defaults change only whitespace and empty values. Invalid numbers, wrong allowed values and duplicate identifiers can remain in the copied CSV.

Network use

After you choose Sign in with GitHub, github.com receives the public client ID, profile scope and device-flow polling requests. After sign-in, api.github.com receives an authenticated query for your sponsorship tier and total payment; neither host receives vault data. Successful checks last seven days; network failures can retry after six hours, and Refresh requests an earlier check.

Read the full network disclosure

Questions or ideas?

Tell me what is broken in CSV Rule Check, or what it should do next.

Send feedback

CSV Rule Check 1.1.0, MIT license

MIT · no telemetry · core features free