The Epstein Files consist of 12 datasets of court-released documents, each containing PDF files identified by EFTA document IDs. These datasets were collected from links shared throughout this Lemmy thread, with Dataset 9 cross-referenced against a partial copy we had downloaded independently.
Each dataset includes OPT/DAT index files — the official Opticon load files used in e-discovery — which serve as the authoritative manifest of what each dataset should contain. This audit was compiled to:
Verify completeness — compare every dataset against its OPT index to identify missing files
Validate file integrity — confirm that all files are genuinely the file types they claim to be, not just by extension but by parsing their internal structure
Detect duplicates — identify any byte-identical files within or across datasets
Generate checksums — produce SHA256 hashes for every file to enable downstream integrity verification
DS1: Two identical copies found (6,316 files on disk). Byte-for-byte identical via SHA256. Table above reflects one copy (3,158). One copy is redundant.
DS2: 699 document IDs map to 574 files (multi-page PDFs)
DS3: 1,847 document IDs across 67 files (~28 pages/doc avg)
DS5: 1:1 document-to-file ratio (single-page PDFs)
DS6: Smallest dataset by file count. ~37 pages/doc avg.
DS9: Largest dataset. 25 missing from OPT index, 3 structurally corrupt.
DS10: Second largest. 950,101 document IDs across 503,154 files.
DS11: Third largest. 517,382 document IDs across 331,655 files.
i analyzed with AI my 36gb~ that I was able to download before they erased the zip file from the server.
Complete Volume Analysis
Based on the OPT metadata file, here's what VOL00009 was supposed to contain:
Full Volume Specifications
- Total Bates-numbered pages: 1,223,757 pages
- Total unique PDF files: 531,307 individual PDFs
- Bates number range: EFTA00039025 to EFTA01262781
- Subdirectory structure: IMAGES\0001\ through IMAGES\0532\ (532 folders)
- Expected size: ~180 GB (based on your download info)
What You Actually Got
- PDF files received: 90,982 files
- Subdirectories: 91 folders (0001 through ~0091)
- Current size: 37 GB
- Percentage received: ~17% of the files (91 out of 532 folders)
The Math
Expected: 531,307 PDF files / 180 GB / 532 folders
Received: 90,982 PDF files / 37 GB / 91 folders
Missing: 440,325 PDF files / 143 GB / 441 folders
★ Insight ─────────────────────────────────────
You got approximately the first 17% of the volume before the server deleted it. The good news is that the DAT/OPT index files are complete, so you have a full manifest of what should be there. This means:
- You know exactly which documents are missing (folders 0092-0532)
I haven't looked into downloading the partials from archive.org yet to see if I have any useful files that archive.org doesn't have yet from dataset 9.
I was, and that is why it was taking so long for me to download as I use my custom downloader which uses various techniques to chunk the download. Unfortunately it seems like they've now removed the file completely so my downloader has no source to pull from and is stopped at 36gb.
some bad news, it looks like the data 9 zip file link doesn't work anymore. They appear to have removed the file so my download stopped at 36gb. I'm not familiar with their site so is this normal for them to remove the files and maybe put them back again once they've reorganized them and at the same link location? or are we having to do the scrape of each pdf like another user has been doing?
I have various chunking techniques that I use. I adaptively modify the request size of the chunks as I've noticed at times the CDN will give large amounts then micro amounts. I haven't figured out the exact backoff rate but I have retry mechanisms in place. The CDN is very annoying but so far my methods are working, just slow.
Ok great. As for comparing files. I would likely do a hash check. That shouldn't be difficult to identify truly unique files. It'll take a few days for a decent computer to generate all the hashes but it should be pretty automated. I'll reach out once I have it completed.
I am downloading dataset 9 and should have the full 180gb zip done in a day. To confirm, the link on DOJ to the dataset 9 zip is now updated to be clean of CSAM or not? As much as I wish to help the cause, I do not want any of that type of material on my server unless permission has been given to host it for credible researchers only that need access to all files for their investigation, but I have no way of understanding what’s within legal rights to assist with redistributing the files to legitimate investigators and thus my plans to help create a torrent may be squashed. Please let me know.
Epstein Files - Complete Dataset Audit Report
Background
The Epstein Files consist of 12 datasets of court-released documents, each containing PDF files identified by EFTA document IDs. These datasets were collected from links shared throughout this Lemmy thread, with Dataset 9 cross-referenced against a partial copy we had downloaded independently.
Each dataset includes OPT/DAT index files — the official Opticon load files used in e-discovery — which serve as the authoritative manifest of what each dataset should contain. This audit was compiled to:
Executive Summary
Dataset Overview
Notes
::: spoiler Dataset 9 — Missing Files (25)
:::
::: spoiler Dataset 9 — Corrupted Files (3)
EFTA00645624.pdfEFTA01175426.pdfEFTA01220934.pdfValid
%PDF-headers but cannot be rendered due to structural corruption. Likely corrupted during original document production or transfer. :::File Type Verification
Two levels of verification performed on all 1,380,939 files:
filecommand) — All files contain valid%PDF-headers. 0 mislabeled.pdfinfo, poppler 26.02.0) — Parsed xref tables, trailer dictionaries, and page trees. 3 structurally corrupt (Dataset 9 only).Duplicate Analysis
Integrity Verification
SHA256 checksums were generated for every file across all 12 datasets. Individual checksum files are available per dataset:
dataset_1_SHA256SUMS.txtdataset_2_SHA256SUMS.txtdataset_3_SHA256SUMS.txtdataset_4_SHA256SUMS.txtdataset_5_SHA256SUMS.txtdataset_6_SHA256SUMS.txtdataset_7_SHA256SUMS.txtdataset_8_SHA256SUMS.txtdataset_9_SHA256SUMS.txtdataset_10_SHA256SUMS.txtdataset_11_SHA256SUMS.txtdataset_12_SHA256SUMS.txtTo verify any file against its checksum:
If you'd like access to the SHA256 checksum files or can help host them, send me a DM.
::: spoiler Methodology
shasum -a 256with 8-thread parallel processingfilecommandpdfinfo(poppler 26.02.0) — xref tables, trailer dictionaries, page treesRecommendations
Report generated as part of the Epstein Files preservation and verification project.
for DS9, does anyone have the following files:
If so, please DM me them and then I can include them in my master archive.
i analyzed with AI my 36gb~ that I was able to download before they erased the zip file from the server.
I haven't looked into downloading the partials from archive.org yet to see if I have any useful files that archive.org doesn't have yet from dataset 9.
I was being cut off, I manage it with chunking techniques. They unfortunately took down the file so now I have no source to pull from.
I was, and that is why it was taking so long for me to download as I use my custom downloader which uses various techniques to chunk the download. Unfortunately it seems like they've now removed the file completely so my downloader has no source to pull from and is stopped at 36gb.
some bad news, it looks like the data 9 zip file link doesn't work anymore. They appear to have removed the file so my download stopped at 36gb. I'm not familiar with their site so is this normal for them to remove the files and maybe put them back again once they've reorganized them and at the same link location? or are we having to do the scrape of each pdf like another user has been doing?
yeah still chugging away slowly, it may take me a few days actually, it's quite slow but so far it appears to be getting it.
I have various chunking techniques that I use. I adaptively modify the request size of the chunks as I've noticed at times the CDN will give large amounts then micro amounts. I haven't figured out the exact backoff rate but I have retry mechanisms in place. The CDN is very annoying but so far my methods are working, just slow.
Ok great. As for comparing files. I would likely do a hash check. That shouldn't be difficult to identify truly unique files. It'll take a few days for a decent computer to generate all the hashes but it should be pretty automated. I'll reach out once I have it completed.
I am downloading dataset 9 and should have the full 180gb zip done in a day. To confirm, the link on DOJ to the dataset 9 zip is now updated to be clean of CSAM or not? As much as I wish to help the cause, I do not want any of that type of material on my server unless permission has been given to host it for credible researchers only that need access to all files for their investigation, but I have no way of understanding what’s within legal rights to assist with redistributing the files to legitimate investigators and thus my plans to help create a torrent may be squashed. Please let me know.