Before you download, the finished file is checked on your device. Pages without text get searchable text while today’s OCR allowance covers them (free plan: 5 pages a day; Pro: no limit), and pages beyond it are listed so you can run OCR on them. Pages whose images are above 300 dpi are listed. The file is set to open on page 1 at 100% with the bookmarks showing, in viewers that follow a PDF’s opening settings. Its size is compared with the limit you choose, and a bundle over it can be split into volumes: the numbering runs on, so volume 2 starts where volume 1 stopped, and each volume opens with an index of the documents it holds, linked to their first pages. Leak Check’s byte-level checks — earlier saved versions, orphaned objects and carriers such as attachments, scripts and metadata — run on the file you download, and what they find is reported first. It is set up the way court e-bundle guidance usually asks; check your court’s practice direction for its own rules. Nothing is uploaded.
How it works
- Drop the documents — the court checklist and Court bundle are already chosen
- Check where each file landed, order the exhibits, and choose the page-number style and the size limit
- Build the bundle, read the checks — searchable text, image resolution, size, hidden content — and download it, in volumes if it is over the limit
Questions people ask
Do the index links and bookmarks work in any PDF viewer?
They are standard PDF links and bookmarks, which most desktop PDF readers show, and many browser viewers too. The opening view is different: the file is set to open on page 1 at 100% with the bookmarks showing, in viewers that follow a PDF’s opening settings, and many browser viewers ignore those settings and open their own way. The links point inside the file, so they keep working when the bundle is emailed or uploaded; in a bundle split into volumes, each volume’s index links only to the documents that volume holds.
What does the hidden-content check look for?
It runs Leak Check’s byte-level checks on the finished bundle — the file you download: earlier saved versions inside the bundle file (one Bindery writes fresh has none, and the check confirms it), orphaned objects that still hold text or pictures, and carriers such as unapplied redaction marks, hidden form values, switched-off layers, thumbnails, bookmark titles with personal data, metadata, attachments and scripts. With nothing found the report says none of its checks found recoverable content, never that the file is safe. It does not judge what the pages show: text under a black box drawn in a source file needs Leak Check’s full scan of that file, and Redact to remove it, before the file goes into the bundle.
Why are images above 300 dpi reported?
Pictures scanned at a high resolution make a bundle large and slow to page through, and rarely look sharper on screen at normal zoom. The check lists the pages whose images are above 300 dpi; you can leave them, or have the bundle’s pictures re-encoded at up to about 300 dpi with the engine Compress uses — it changes pictures only and never turns text into pixels, though it re-encodes every picture in the bundle, not just the flagged ones.
Is it free, and is anything uploaded?
A bundle is one of your 3 free jobs a day, however many documents it holds; files can be up to 25 MB each, pages without text count toward the 5 free OCR pages a day, and free PDFs carry a small “Made with Bindery” line on every page, which Pro removes along with the caps. Merging, numbering, OCR and every check run in your browser tab, so the documents never leave your device.