Use a PSD when you are editing raster imagery layer by layer, an AI file when you are building resolution-independent vector artwork, an INDD file when you are laying out multi-page documents with linked assets, and a PDF when you need to deliver or archive a finished, print- or view-ready page that others should not restructure. The correct choice follows the editing stage and the recipient's needs, not file prestige.

How Each Format Stores Its Data

A PSD (Photoshop document) is a layered raster container. It stores pixel grids plus per-layer masks, adjustment layers, smart objects, blend modes, and editable type. The mechanism that matters is the raster grid: resolution is baked into the pixel dimensions, so a 300 ppi document at 8 by 10 inches carries roughly 2,400 by 3,000 pixels. Enlarge beyond that and interpolation invents pixels rather than recovering detail. Smart objects are the exception, because they can embed a vector or a higher-resolution source that Photoshop re-renders.

An AI (Adobe Illustrator) file is built on vector paths defined by mathematical coordinates, fills, and strokes. Because geometry is described rather than sampled, artwork scales without pixel loss up to the output device's limit. The counterintuitive detail: an AI file can hold embedded raster images and live type, so "vector file" does not guarantee vector contents. A scan placed in Illustrator stays raster inside a vector wrapper.

An INDD (InDesign) file is a layout container, not an image repository. It stores frames, master pages, styles, and links to external assets. The actual images usually live elsewhere on disk, which is why moving an INDD without its Links folder breaks previews. One plain-language way to hold this: the INDD is the blueprint, and the photos, fonts, and logos are materials stored in a separate warehouse.

A PDF (Portable Document Format) is a final-form description of pages. It can embed fonts and compress images, and it can preserve vector paths, but its main job is faithful rendering rather than layered editing. A PDF exported "for print" keeps high-resolution imagery; one exported "for web" downsamples it, often to 150 ppi or lower. That export setting, not the extension, decides whether the file is press-grade.

Quantified Context: Resolution, Color, and File Behavior

The thresholds that drive format choice are measurable. Commercial printing typically wants 300 ppi at final placed size for raster images; large-format banners are often acceptable at 100 to 150 ppi because viewing distance grows. Vector art has no ppi ceiling, which is why logos belong in AI or a vector PDF rather than a flattened PSD.

Color mode is a second threshold. Print workflows generally use CMYK, while screens use RGB. A PSD or AI can hold either and convert later, but a PDF exported without conversion may carry an RGB profile into a CMYK press and shift colors. Conversion factors between color spaces are device- and profile-dependent, so no universal number exists; treat any claimed fixed conversion as a red flag.

File size tells a practical story. A layered PSD for a single 8 by 10 inch image at 300 ppi can run from tens to hundreds of megabytes depending on layer count. The same image flattened and exported as a press PDF often shrinks substantially. A multi-page INDD with dozens of linked images may be small itself while its Links folder carries gigabytes. According to the PDF specification maintained by ISO, PDF is designed for reliable cross-platform rendering, which is the property that makes it the delivery default (ISO 32000).

Timeline: How a Project Moves Through Formats

Stage Working file Output file Typical threshold
Concept and image editing PSD none yet 300 ppi at final size
Logo and icon construction AI vector PDF or SVG no resolution limit
Multi-page layout INDD (with links) press PDF 0.125 inch bleed typical
Client review PDF proof annotated PDF low-res, often 150 ppi
Printer handoff packaged INDD PDF/X fonts embedded, CMYK
Long-term archive original working file PDF/A ISO archival profile

The timeline matters because formats are stage-specific. Sending a PSD to a printer forces them to flatten and convert, and sending an INDD to a client who lacks the fonts and links produces a broken preview. The PDF/X family exists precisely to freeze a print-ready state so the recipient does not need the source.

Edge Cases That Break the Simple Rule

Transparency is a classic edge case. A PSD with complex layer blending may not flatten identically in a PDF, so printers sometimes request a flattened TIFF or a PDF/X-4 that supports live transparency. The professional caveat: always ask the output vendor which PDF flavor they accept before export.

Packaged fonts are another edge. An INDD depends on installed fonts; a PDF can embed them. When a recipient lacks a font license, the PDF is the only safe delivery. Conversely, if the client must edit copy, only the INDD (or a shared equivalent) lets them do it without rebuilding the page.

Editable text in a PDF is not guaranteed. Text can be outlined or rasterized during export, so "I sent a PDF, they can edit it" is often false. Vector logos in an AI file remain fully editable; the same logo flattened into a PDF is not.

Red-flag warnings: A "print-ready" PDF exported at 72 ppi will look soft on press. An INDD sent without its Links folder arrives with missing-image placeholders. A PSD flattened to save space destroys every layer you may need later. An AI file with a placed scan is not scale-safe despite its extension. A PDF with unembedded fonts substitutes typefaces on the recipient's machine.

Misconceptions Worth Retiring

The biggest misconception is that one format is "best." Each container optimizes for a different job: PSD for pixel editing, AI for vector geometry, INDD for page assembly, PDF for delivery and archival. Choosing by habit rather than by stage is the real error.

A second misconception is that PDF is always final and uneditable. PDF supports forms, annotations, and even limited editing, and its layered variants preserve structure. The extension describes a rendering contract, not an editability guarantee.

A third is that file size predicts quality. A small PDF can be visually lossless for text and vector art, while a large PSD can still be low-resolution if its pixel dimensions are small. Judge resolution by pixel dimensions and ppi at placed size, not by megabytes.

Practical Actions: Choosing in Under a Minute

Ask four questions in order. First, is the content pixels or paths? Pixels point to PSD; paths point to AI. Second, is it one image or many pages? Many pages point to INDD. Third, does the recipient need to edit the source? If not, PDF. Fourth, what does the output device require? Match the PDF flavor and color mode to the vendor's spec before export.

Concrete steps follow from those answers: Edit photography and composites in PSD, keeping layers until final approval. Build logos, icons, and type-as-art in AI, then export a vector PDF for delivery. Assemble multi-page work in INDD, and package it with fonts and links before handoff. Export a press PDF/X at 300 ppi for raster content and embed all fonts. Keep the layered PSD, AI, and INDD as archive masters; distribute PDFs.

Reconciling thresholds: the 300 ppi figure applies to raster images at final placed size, not to vector art, and not to large-format work viewed from distance. The PDF/X standard applies to print handoff, while PDF/A applies to long-term archiving. These are separate targets, so pick the one your recipient actually named.

Limitations and What the Formats Cannot Do

No format fixes a bad source. Upscaling a 72 ppi image inside a PSD or PDF produces interpolation, not detail. Embedding a low-resolution scan in an AI file does not make it vector. A perfectly packaged INDD still fails if the printer's RIP rejects a linked asset's color profile.

PDF also cannot guarantee identical rendering across every viewer, because rendering engines differ in color management and transparency handling. That is why proofs exist. And no extension guarantees legal or contractual fitness; delivery specs come from the recipient, not the file type. When a vendor, client, or archive gives a written requirement, that requirement outranks any general rule here.