PDF Resolution for Print: Why "I Hit 300 DPI" Is Not the Whole Story

Most print buyers check the resolution box and move on. They hear "300 DPI" once, confirm their file hits it, and assume the job is clean. That assumption causes reprints.

300 DPI is not a finish line. It is a minimum starting point. Whether it is enough depends on output size, viewing distance, substrate, and what kind of artwork is in the file. This guide explains how to think about PDF resolution for print the way a prepress technician does. Buyers submit better files. Shops catch problems before the press does.

What 300 DPI Actually Means (and What It Doesn't)

DPI stands for dots per inch. In the context of raster images inside a PDF, it describes how many pixels are packed into each linear inch of the printed output. At 300 DPI, a 3,000-pixel-wide image prints cleanly at 10 inches wide. That same image at 20 inches wide is only 150 DPI, and it will look soft.

The number attached to a file in your file manager or image editor is the document DPI setting. That is not necessarily the effective resolution at output size. Those two things are frequently different. A file can be tagged as 300 DPI and still be low resolution if it was scaled up after the fact.

Two other points worth locking in:

DPI and PPI are not the same thing. PPI (pixels per inch) describes the pixel density of a raster image. DPI technically describes the output dot pattern of a printer or imagesetter. In common prepress conversation the terms get used interchangeably. Understanding the distinction matters when you are talking to an RIP or a press operator.

Resolution only applies to raster content. Photographs, scanned artwork, raster logos, and placed bitmap images all have a resolution. Vector artwork, paths, type set as outlines, and geometric shapes are resolution-independent. They scale without degradation. Resolution checks that catch a low-res photograph will tell you nothing useful about a vector logo in the same file.

Output Size Changes Everything: The Effective Resolution Problem

Here is the calculation every prepress technician uses:

Effective resolution = native pixel width / output width in inches

A 2,400 x 3,600 pixel photograph placed at 8 x 12 inches is exactly 300 DPI. Scale that photograph to 16 x 24 inches in the layout and the effective resolution drops to 150 DPI. The pixels did not change. The output demand did.

This is why "the original was 300 DPI" is not a useful answer when a file comes in soft. What matters is the effective resolution at the size it will print.

General guidelines by product type:

| Product | Recommended effective resolution | |---|---| | Business cards, brochures, postcards | 300 DPI minimum | | Banners, posters (viewed from 5+ feet) | 150 DPI often acceptable | | Billboards, building wraps | 25 to 72 DPI at output size is common | | Fine-art giclée prints | 360 to 600 DPI preferred | | Newspaper offset | 200 DPI minimum |

Viewing distance is the governing factor. A banner hung 10 feet overhead does not need the same pixel density as a business card held in someone's hand. Shops that apply a flat 300 DPI rule to all jobs will reject usable large-format files. They will also pass soft files that should have been flagged.

Raster vs. Vector: Why Resolution Is the Wrong Question for Half Your File

A well-built print PDF almost always contains both raster and vector elements. The background photograph is raster. The headline type, if it was properly exported, is vector. The company logo may be either, depending on how it was created and how it was placed.

Vector objects carry no resolution. They are described mathematically as paths and fills. They render at whatever the output device's native resolution is, typically 1,200 to 2,400 DPI on a commercial press. You cannot make a vector logo "low resolution." You can, however, accidentally rasterize it during export or PDF creation. That immediately imposes a resolution ceiling.

Common rasterization traps:

• Exporting a PDF with "flatten transparency" set to raster mode
• Saving from a tool that bitmaps all content at a fixed resolution during export
• Embedding a screenshot or low-res PNG of a logo instead of the original vector file

When you are preflighting a PDF, the resolution check should target raster content specifically. Flagging a 72 DPI vector object is a false alarm. Missing a 96 DPI embedded JPEG in the same file is a real problem.

PDF font embedding for print has a related issue. Fonts that are not properly embedded or outlined can behave unpredictably on press even when resolution looks fine on screen.

When 300 DPI Is Not Enough, and When Lower Can Be Fine

When 300 DPI may not be enough:

• Fine-art reproduction prints where the customer expects photographic sharpness at close viewing distance
• Products with fine halftone screens or high line-screen rulings (175 lpi or above), where the recommended image resolution is 1.5 to 2 times the line screen. That puts the target at 263 to 350 DPI as a floor, not a ceiling.
• Soft-proofing workflows where a low-res preview was approved but the actual placed image was never resolution-checked

When lower can be acceptable:

• Large-format output sized for viewing at distance (see the table above)
• Screen printing and certain specialty substrates where the print process itself limits output detail regardless of image resolution
• Coarse-texture substrates like canvas or uncoated stock, where the material absorbs fine detail anyway

The substrate matters. A 300 DPI image on coated stock and a 300 DPI image on uncoated offset stock will not look the same. Uncoated paper spreads ink dots, which softens fine detail. On a very coarse stock, sending a 400 DPI image provides no visible benefit over a 300 DPI image. The press and the paper are the limiting factors, not the file.

How Resolution Fits Into a Full Preflight Routine

Resolution is one line item in a complete preflight checklist, not the checklist itself. A file can pass a resolution check and still fail press for a dozen other reasons: missing bleed, incorrect color mode, missing fonts, misset overprints.

Print ready file preflight: 7 errors that cause reprints covers the full list. Within the resolution step, a solid preflight routine looks like this:

1. Identify all raster images in the PDF. Most preflight tools will list each placed image with its effective resolution at output size.
2. Check effective resolution, not document DPI. A 72 DPI document tag on an image placed very small may still be printing at 300 DPI effective. The inverse is also true.
3. Flag anything below threshold for the product type. Use the viewing-distance table to set the right threshold. Do not apply a flat 300 DPI rule to all jobs.
4. Check for accidentally rasterized vector content. If a logo or headline type shows up as a low-resolution raster object, the source file has a problem. It needs to go back to the designer.
5. Note color mode on raster images. An RGB image embedded in a CMYK PDF is a separate problem, but preflight usually surfaces it at the same time. See CMYK vs RGB for print: what it costs your shop for the full breakdown of what that conversion costs.

Tools like Acrobat Pro's Output Preview, PitStop Pro, and callas pdfToolbox will surface effective image resolution per object. Use them. Do not rely on the file's self-reported DPI metadata.

Resolution in Customer-Submitted Files: A Shop's Practical Response

Customer-submitted files are where resolution problems concentrate. Customers often build layouts in tools not designed for commercial print. They grab images from websites or scale photographs up to fit a larger template. By the time the file arrives, the problems are baked in.

A practical shop response:

Set resolution requirements in writing before the job is quoted. Your file submission spec sheet should state minimum effective resolution by product type, not a single universal number.

Build resolution checks into your intake preflight, not your final preflight. Catching a low-res image after proof approval costs everyone time. Catch it when the file comes in.

Give customers a specific, actionable error message. "Your file has a low-resolution image" does not help. "The photograph on page 1 is 96 DPI effective at the print size. We need 300 DPI minimum. Please send the original high-resolution file." does.

Know when to proceed and when to stop. A banner file at 150 DPI effective for a 10-foot viewing distance is probably fine. A business card photograph at 150 DPI effective is not. The decision should be based on output specs, not a reflexive rejection of anything below 300.

When shops use StackFill to publish fillable versions of their print templates, the source PDF is already a finished, press-ready file. That means resolution is locked at the design stage. Customers fill in their name, address, or custom text fields, but they cannot swap in a low-res photograph or scale an image beyond what the template allows. That constraint is a feature. It removes an entire category of customer submission errors before they happen. The approach is covered in detail in how to let customers edit a PDF without changing the design.

Resolution is not the only thing standing between a submitted file and a clean press sheet. But it is one of the few problems that is invisible on screen and obvious in print. Treat 300 DPI as the floor it is. Apply the right standard for the job at hand. Preflight against effective resolution at output size, not the number buried in the file's metadata.

← All posts