Legal & Compliance
Check a public records release for duplicate files
Upload the release as a ZIP and get a list of every file with duplicates, junk files and missing extensions flagged. It does not check or apply redactions.
or drop it here
- ZIP / CSV / XLSX / PDF
- Up to 5,000 files
1 prepared source file · 216 bytes
- Files: 2
- Unique files: 2
- Coverage claim: inventory only
file-inventory.csv · organized-source.zip · findings.csv · manifest.json
One clear job, from source to download
- 1
Add the source
Supported formats and limits are visible before the upload.
- 2
Confirm the settings
Review the exact source, options, units and access before processing.
- 3
Inspect and download
Check the preview and warnings, then unlock the complete package.
An inventory of your records release before it goes out
Your release set goes in
You upload the release as a ZIP file. CSV, XLSX and PDF sources are accepted too. One run takes up to 5,000 files, and a larger set is rejected rather than cut short. There are no settings to choose. The checker only records facts it can read from the files you supplied. It is a standard tool, included in your 3 free jobs a day with a free account.
The inventory and the flagged files
You get file-inventory.csv, findings.csv, a copy of the release as organized-source.zip and manifest.json. The inventory lists every file with its proposed name, its extension and a checksum, a short code computed from the file content. Files with matching checksums are grouped as duplicates even when their names differ. The findings flag junk such as system leftovers and empty entries, plus files without an extension. Your source archive is not changed.
What stays with the releasing authority
The inventory shows what is in the set at the time of the run. Many offices keep it as a receipt of what left their custody. It does not check redactions. It does not say whether an exemption was applied correctly, whether every responsive record was found, or whether visible or hidden content is safe to disclose. Those decisions stay with the releasing authority and the people who advise it on the law.
Questions before you run it
Does this check whether the records were redacted properly?
No. It inventories what sits in the archive and never judges whether an exemption was applied or whether visible or hidden content is safe to disclose. That decision stays with the releasing authority.
How are duplicate records detected inside the archive?
Every file is hashed and files whose content hashes match are grouped as duplicates, even when the filenames differ. The inventory keeps the proposed filename beside the hash so you can choose which copy to release.
What counts as a junk file in the findings?
Items that do not belong in a release set, such as operating-system leftovers and empty entries. Files with no extension are flagged separately because they often fail to open for the requester.
What can I upload, and how large can the release set be?
ZIP, CSV, XLSX and PDF sources are accepted, up to 5,000 files in one run. A source over that ceiling is rejected rather than truncated.
Can the inventory serve as a record of what left our custody?
file-inventory.csv and the manifest capture proposed filenames, extensions and hashes at the moment of the run, which is the receipt most offices keep. It records the set that was assembled; it does not certify that the response was complete.