Drop the file. We tell you what is in it — and what we could not read.

Drop your file here or click to choose · CSV, TSV, Excel, JSON, PDF, or zip · a zipped shapefile bundle counts ⚠ PDFs rarely work — across our last 12 we read a table out of one, and none reached a publishable archive. The same data as a spreadsheet or CSV gets much further.

csvxlsxpdfshp / zip → confirmed on your values · refused with a reason → ExcelGISDarwin CoreReport

Nothing stored — the mapping stays, the rows go · Free until 1 September 2026, 00:00 UTC · No account

See a real sample report — a 5,271-record government waterfowl survey, with the archive, the questions and the findings, if you would rather look before uploading.

What goes in

CSV, TSV, Excel (.xlsx/.xlsm), JSON, PDF, and zips — a zipped shapefile bundle counts, and a bare .dbf works. .json and .pdf are read by content, not by name; .xls and .xlsb are refused by name rather than failed silently. PDFs rarely work yet — if the same data exists as a spreadsheet, drop that.

Just have column names, not a file yet? Paste them below and see what a shapefile export would do to them — no upload, nothing saved.

One name per line or comma-separated. Checks the 10-character truncation cap, collisions once cut, and the 255-field limit — what a shapefile export would do to them.

What comes out

Click any tool. Filled dot we build today · hollow on the roadmap.

How we checked our own work

We audited 5,064 occurrence records that were already published to GBIF — they had passed the pipeline and were being served. Of GBIF's own OccurrenceIssue codes we are able to raise, 8 in total, none applied to these records. We returned 4,268 findings of our own.

5,064records already published

0findings in GBIF's vocabulary

4,268findings from ours

31.7%of records came back clean

Every code we raised carries the FS_ prefix, which means it is ours and states its own warrant — never GBIF's name carrying our meaning:

FS_COORDINATE_UNCERTAINTY_ABSENT 1,972
FS_PRECISION_EXCEEDS_UNCERTAINTY 1,230
FS_COORDINATE_PRECISION_LOW 1,028
FS_DATE_PRECISION_REDUCED 38

And not one of them is an error — nothing here says a record is wrong as stated. 3,458 of these records carry something a downstream user may need and a receiving body does not check. GBIF's validator answers will this load, and these had already loaded — the two questions are simply different ones.

One file, 5,064 records, drawn from GBIF's own API and not chosen by us. A second file from the same source, different taxa: 400 records, 219 findings, again none of them GBIF's, 55.0% clean. Every figure here is read from ops/data.json, regenerated by re-running the audit over the raw records — none is typed into this page.

How this differs from GBIF's validator

Their validator checks an archive you have already built and answers will this load. We start from the file you actually have, confirm each column against its own values — a column named latitude holding longitudes is real, and a name match cannot see it — and refuse what is genuinely ambiguous. The two reports do not overlap: measured above, on records already published to GBIF, nothing in their vocabulary fired and our audit still had plenty to say. The sample report below is the same story on a different file — a well-made government survey where 20 terms map, the archive builds, and 399 of the 400 records we sampled still carried something worth telling you about.

How it works

We open files you cannot — shapefiles, zips, locked-up tables

We check every column against its own values, not its header

We build the file your receiver takes, and list what is missing

We never guess — an ambiguous column is refused, by name

We never grade you — no score, no badge, no seal

We never keep your records — the mapping stays, the rows go

Three things worth knowing

Read the refusals first. One line per column we could not read, and why. Expect a handful, not hundreds. All 63 codes.

Answer anything we ask. We only ask when only you can settle it.

Still run GBIF's validator before publishing. We do not replace it.

Drop the file. We tell you what is in it — and what we could not read.

What we refused to interpret

Answer a few questions and we will re-run your file

Your file, drawn

Summary

Every column in your file

The data-quality audit

Does the area you typed match the boundary you drew?

What we can still hand you

Finish your archive

First, things only you can settle

Which one did you mean?