Workflow 8 min read 19 October 2026

PDF Portfolios: Assembling, Navigating, and Extracting Multi-File PDF Packages

Q: How are PDF portfolios used in legal discovery?

In US federal litigation , the EDRM (Electronic Discovery Reference Model) specifies how electronically stored information (ESI) should be collected, processed, and produced. PDF portfolios are used in some discovery production workflows to bundle a document with its metadata: the PDF representation of the document (with Bates numbers) plus the original native file (if required under FRCP Rule 34), plus an extracted text file and metadata CSV, all wrapped in a portfolio. The /Collection schema defines fields matching the metadata fields required by the receiving party (custodian, date, document type, privilege status). Litigation support tools (Relativity, Nuix, Concordance) can both create and import these portfolio packages.

A PDF Portfolio embeds multiple files of any type inside a single .pdf container. This guide explains how portfolios differ from merged PDFs, how to create and extract them, the Navigator UI, and use cases in legal discovery, financial reporting, and technical documentation.

A PDF Portfolio — also called a PDF Package or PDF Collection — is a PDF container that holds multiple files of any type inside a single .pdf file. Unlike a merged PDF where everything is flattened into one document, each file in a portfolio retains its original format: a Word document stays as a Word document, an Excel spreadsheet stays as an Excel spreadsheet, a PDF stays as a PDF. The portfolio provides a navigable wrapper with a customisable cover sheet, while the embedded files can be individually opened, extracted, or printed. PDF Portfolios are defined in ISO 32000-2:2017 (PDF 2.0) via the /Collection dictionary. They were introduced in PDF 1.7 / Acrobat 8. Legal discovery production sets, financial reporting packages, and technical documentation bundles are the primary use cases.

How portfolios differ from merged PDFs

The distinction matters significantly in practice: Merged PDF — All pages are flattened into a single continuous PDF page sequence. The individual source files no longer exist as distinct entities. Metadata, bookmarks, and other file-specific information may be lost or merged. A merged PDF is a single document. PDF Portfolio — The source files are embedded as file attachments. They remain individually accessible. A Word document can be opened directly in Word from within the portfolio; a PDF can be viewed as its own PDF. The portfolio document itself is a navigable index — the embedded files are not visible as pages unless explicitly opened. Content searching typically searches only the metadata and index, not the full text of all embedded files (unless the viewer indexes them). When to use portfolios: - Legal discovery production where documents must be delivered in original format alongside metadata - Financial closing binders where individual transaction documents need to be referenced independently - Technical documentation packages (specifications, drawings, test reports) where each document has its own lifecycle - Archival packages (PDF/A-3) where original source files must accompany the archival representation When to use merged PDFs: - Submission packages where a single unified document is required - Printing multiple documents as a single print job - Combining related chapters or sections that form a logical unit

Portfolio structure: the /Collection dictionary

Internally, a PDF Portfolio uses the /Collection dictionary in the document catalogue. The key entries: /Schema — Defines the metadata fields for the embedded files that appear as columns in the portfolio navigator (Filename, Description, Date Modified, Size, etc.). Each schema field has a type (Text, Date, Number) and display properties. /D (default sort field) — Specifies which schema field is used for default sorting. /View — Controls the portfolio navigator display mode: /D (detail list), /T (tiled thumbnails), /H (hidden — the portfolio acts as an envelope without a visible navigator). /Sort — Default sort direction (ascending/descending). The embedded files themselves are stored as embedded file streams in the PDF's embedded files name tree (/EmbeddedFiles in the /Names dictionary). Each embedded file is a stream object with /Type /EmbeddedFile and attributes including creation date, modification date, MIME type, and a checksum. File attachment annotations reference these embedded file streams. Navigator / Cover Sheet — The portfolio cover sheet is a standard PDF page (or sequence of pages) that forms the visible content of the portfolio document itself. Users without a portfolio-aware viewer see this cover page. Acrobat displays the portfolio navigator alongside it.

Creating and extracting portfolios

Adobe Acrobat Pro — File > Create > PDF Portfolio provides a wizard for assembling portfolios. You can add files, arrange them, customise the navigator layout, and add metadata. File > Export All Files (from within a portfolio) extracts all embedded files. Command-line with pdftk — pdftk supports attaching and unpacking file attachments: pdftk input.pdf attach_files doc1.pdf doc2.xlsx output portfolio.pdf creates a PDF with file attachments (not a full portfolio with /Collection, but suitable for simpler use cases). pdftk portfolio.pdf unpack_files output_directory/ extracts embedded files. Python with pypdf — pypdf can read embedded files from portfolios: iterate over reader.attachments to access embedded file data. For creating portfolios with a full /Collection structure, lower-level manipulation with pypdf's PDF writer or pikepdf is needed. PDF/A-3 portfolios — For archival purposes, the embedded files can conform to PDF/A-3 (which allows arbitrary embedded files). The portfolio container itself should be PDF/A-3 compliant if long-term preservation is required. The /AFRelationship entry in each embedded file specification declares whether the file is a source, data, alternative, or supplement to the container PDF. This is the same mechanism used by ZUGFeRD/Factur-X invoice PDFs.

Frequently asked questions

Can all PDF viewers open PDF portfolios?

Basic portfolio support — displaying the cover sheet and a file list — is available in Adobe Acrobat Reader (free), Adobe Acrobat Pro, and Foxit Reader. However, the interactive portfolio navigator with sorting, filtering, and thumbnail previews is primarily an Acrobat experience. Many PDF viewers (Chrome built-in, Firefox PDF.js, Apple Preview) display the portfolio cover sheet as a normal PDF and may show embedded files in a list, but do not provide the full portfolio navigation interface. For organisations distributing portfolios to general users, a well-designed cover sheet with clear instructions for extracting files is essential, since recipients may not have Acrobat.

What is the difference between a PDF Portfolio and a PDF with file attachments?

A PDF with file attachments is any PDF that has embedded files in its /EmbeddedFiles name tree — accessible via the paperclip icon in Acrobat's attachments panel. This is the mechanism File Attachment annotations use, and it's also what pdftk's attach_files command creates. A PDF Portfolio is a specific enhancement: it adds the /Collection dictionary to the document catalogue, which defines schema metadata fields, navigator display settings, and sort order. The /Collection dictionary is what tells Acrobat to display the portfolio navigator UI. Without /Collection, the PDF is just a regular PDF with file attachments — still useful for bundling documents, but without the structured navigator experience.

How are PDF portfolios used in legal discovery?

In US federal litigation, the EDRM (Electronic Discovery Reference Model) specifies how electronically stored information (ESI) should be collected, processed, and produced. PDF portfolios are used in some discovery production workflows to bundle a document with its metadata: the PDF representation of the document (with Bates numbers) plus the original native file (if required under FRCP Rule 34), plus an extracted text file and metadata CSV, all wrapped in a portfolio. The /Collection schema defines fields matching the metadata fields required by the receiving party (custodian, date, document type, privilege status). Litigation support tools (Relativity, Nuix, Concordance) can both create and import these portfolio packages.

Try it yourself

Everything in this article can be done directly in the free PDFTheGuide editor — no account required.

Merge PDF Edit PDF Open editor