A PDF Portfolio is a container of component files, rather than necessarily one continuous sequence of PDF pages. A browser or email preview may show only a cover or a request to open it elsewhere. Confirm the document structure before concluding that the portfolio's images were deleted. If the recipient needs a simple page-by-page review, prepare a separate merged PDF using the supported source files.
Check whether you sent a container or pages
Open the delivery copy in an application that supports its structure. List the component filenames and types. Separately record the number of ordinary PDF pages available to a basic viewer. Those counts answer different questions; ten attached files are not automatically ten directly readable pages.
Keep original component files and the portfolio master. A collection may intentionally preserve video, spreadsheets or editable documents that cannot be represented fully as static pages. Decide what the recipient needs to inspect instead of converting every component without a purpose.
Match the structure to the receiving workflow
Adobe's Portfolio overview distinguishes the container from a merged PDF and describes limitations in browsers and other viewers. Its Combine files guide explains creating one sequential PDF with arranged pages. These are Acrobat workflows; Imagild artwork delivery does not automatically create either structure.
For a simple visual review, choose supported static inputs, arrange them in the required order and create a labeled viewing copy. For a source-file handoff, retain the components with a manifest and explicit instructions. Do not imply that a static merged PDF preserves an embedded video's playback or a spreadsheet's calculations.
A hypothetical creative-proposal package
Suppose a proposal includes six image pages, an MP4 concept preview and an editable slide deck. A Portfolio keeps these as components, but the client's browser exposes only a cover. A proposed handoff provides a sequential PDF of the six review pages and clearly identified authorized access to the other materials.
The review table lists each component, its intended purpose and the recipient's viewing route. This is a proposed compatibility test, not a verified customer package. Confirm that the static review copy contains all six approved pages and that the recipient knows which files remain editable or playable elsewhere.
Test the actual receiving preview
Accept when the recipient can view the intended material through the agreed route and every component has an unambiguous role. Reject a cover-only browser preview presented as proof that the full proposal is available, or a flattened substitute described as preserving source editability. Open the transferred delivery copy, not a creator-only session.
Keep the component manifest, viewing copy and editable sources separately labeled. Avoid obsolete web-publication instructions that depend on discontinued browser technologies. Imagild's Skills can develop the visual assets; document packaging and viewer compatibility remain external. A trustworthy package tells the recipient what the container holds and how to inspect the actual approved content.