How FileDigest Works
A user-facing overview of FileDigest document preparation and the pipeline that runs after you upload.
FileDigest turns supported source documents into AI-ready artifacts you can inspect before using them in ChatGPT, Claude, RAG prep, or analyst workflows.
The core output is a readable digest.md plus a structured manifest.json. The digest is for humans and LLM context windows. The manifest is for file-level review, metadata checks, and repeatable downstream workflows.
Upload a document packet
Start with PDFs, DOCX, PPTX, TXT, Markdown, HTML, or a ZIP bundle containing supported files.
Choose processing options
Select fast text extraction for normal jobs, accurate tables when structure matters more, or OCR when your plan includes scanned-document processing.
Review the result
Open the completed job to inspect the digest, manifest, parsed files, warnings, failed files, and token estimates.
Download private artifacts
Download digest.md and manifest.json through authenticated, short-lived links tied to your account.
FileDigest is intentionally narrow: it prepares source documents for AI use. It is not a chat app, not a public file host, and not a replacement for human review.
What happens after you upload
FileDigest separates upload, validation, processing, and artifact download so each step is visible.
Create a job
The workbench checks file count, job size, estimated output tokens, OCR access, and monthly quota.
Upload privately
Your browser uploads selected files to private storage paths assigned to your job.
Register files
After upload, FileDigest confirms the files exist and prepares the packet for processing.
Generate artifacts
The processing engine converts supported inputs into digest.md and manifest.json.
Review the job
The job page shows status, warnings, failed files, digest preview, manifest preview, and private downloads.
Ready to try it? Follow Create your first digest, or call the same pipeline from code with the API.