Press Release Photo Specs: What Editors Actually Want Attached

You ship the announcement at 6:00 AM Eastern: founder photo, product hero, three lifestyle shots. By 9:00 AM, three trade publications have run the story with your photos. By 9:30 AM, the AP wire desk has bounced the entire pitch because the founder photo arrived as a 22 MB Adobe RGB TIFF that their inbox auto-rejected. The story still runs through the trade outlets, but you lose the wire pickup that would have multiplied the coverage by ten. The difference is a single export setting.

Wire services and newsroom inbound systems have file-size caps, format expectations, and metadata requirements that are mostly invisible until your pitch hits the trash. AP, Reuters, Business Wire, PR Newswire, and the editorial inboxes at major trade publications all run automated triage on attached photos before a human ever sees the pitch. Get the specs right and your photo runs in 40 outlets within six hours; get them wrong and it sits in a queue forever while your competitor's better-prepped announcement gets the coverage. This guide is the spec sheet you can hand to your photographer and your PR coordinator so the pitch never bounces.

The resolution editors actually want

AP, Reuters, and most major newsrooms expect press release photos at a minimum of 2400 pixels on the long edge for web publication, and at least 3600 pixels for any photo that might run in print. The myth that you need 300 DPI tied to a specific physical size is outdated; what desk editors care about is pixel count, because they crop and re-export at the publication's own target sizes. Send a 3600x2400 JPG and you cover both web and print without any back-and-forth.

Background: how wire services triage photos

Major wires have run automated photo triage since roughly 2015. The ingest system reads file headers, checks EXIF and IPTC fields, scans for resolution and color space, then routes the pitch to either a human editor's queue or directly to the trash. Photos missing the Headline, Caption, and Credit fields are auto-rejected at most wires because the desk can't legally republish without attribution. Photos in Adobe RGB or ProPhoto RGB get color-shifted during CMS ingest and are flagged for re-export. Photos over 10 MB exceed the SMTP attachment limit on the wire's automated forwarder. Knowing the triage rules is the difference between coverage and silence.

Aspect ratio: ship multiple crops or pick 3:2

News photo display systems are built around 3:2 landscape, but social cards favor 16:9 and 1:1. The cleanest pitch package includes the master at native ratio plus two pre-cropped variants: 3:2 for editorial display and 1:1 for newsroom social teams. Trade publications increasingly want 16:9 hero crops for newsletter embeds. If you're producing crops in bulk for a campaign, run the math through the aspect ratio calculator to confirm pixel dimensions across each target.

File size: the 10 MB ceiling

Most editorial inbound systems and PR distribution wires (PR Newswire, Business Wire, Cision) cap individual photo attachments at 10 MB, with practical sweet spots between 3 and 6 MB for a 3600-pixel JPG. Reuters' Pictures intake system limits to 20 MB but recommends staying below 8 MB for fastest desk review. Anything larger gets bounced or held for review. Export at JPG quality 85, which usually lands a 3600-pixel photo around 4 MB depending on subject complexity. If the file is bigger, run it through JPG compressor with a target output size; the tool lets you specify "max 5 MB" instead of guessing at quality sliders.

TIFF to JPG: converting masters cleanly

Studio photographers often deliver press shots as 16-bit TIFF masters that are 80 to 200 MB each. Don't forward those directly. Convert to JPG quality 90 for archive-quality web use, or quality 85 for distribution. The conversion preserves visible detail at all editorial print sizes while shrinking the file by 95 percent or more. Batch through TIFF to JPG if you have a full shoot to prep.

Caption and credit metadata: the IPTC fields that matter

Wire services require five IPTC fields populated on every photo: Headline, Caption (Description), Credit, Copyright Notice, and Object Name. Newsrooms ingest these directly into their CMS, so a properly tagged JPG can flow from inbox to published article with no human retyping. Set the Credit field to "Photo: [Photographer Name]/[Organization]" and Copyright to the full year and rights holder. Verify the fields stuck by running the exported file through image info before sending.

DPI confusion: what it means and doesn't

DPI (dots per inch) is purely a print hint stored in the JPG header. It doesn't affect pixel count or visible quality on screen. A 3600-pixel photo prints at 12 inches wide at 300 DPI or 18 inches wide at 200 DPI; same file, different metadata. If a press release asks for "300 DPI photos," they really mean "high-resolution photos that will print well at the size we plan to use," which translates to at least 3000 pixels on the long edge. Update DPI metadata without re-sampling using the DPI converter.

Color profile: sRGB, always

Adobe RGB and ProPhoto RGB look incredible in your editing app and produce shifted, dull colors the moment a newsroom CMS strips the profile. Convert to sRGB before export. Every browser, every social platform, every wire system assumes sRGB. If you don't know what profile is currently embedded, run the file through image info to read the ICC tag.

The one-page checklist for PR teams

Before you send a pitch with attached photos: confirm 2400 pixels minimum on the long edge (3600 if print is possible), JPG quality 85, under 6 MB per file, sRGB color space, IPTC headline and caption populated, credit and copyright fields populated, and at least two aspect-ratio variants (native plus 1:1). Attach no more than four photos per pitch email; link the rest via a Dropbox or Google Drive folder with naming convention "YYYY-MM-DD_Subject_Variant.jpg".

Headshots versus product shots versus event shots

The three press-release photo types have slightly different specs. Executive headshots: vertical or square, 2400 pixels minimum, professional studio lighting, sRGB. Product shots: clean background (white or neutral gray), 3600 pixels minimum so editors can crop tight. Event shots (launch parties, conferences, ceremonies): 4000 pixels with multiple frame options (wide, medium, tight) since editors prefer to choose their own crop from the same moment.

Embargo handling and FTP delivery

Major announcements often involve embargoed photos delivered ahead of the public release. Wire services use timestamped FTP folders (PR Newswire and Business Wire both still operate FTP intake) where you upload pre-embargo and they release at the agreed timestamp. The naming convention typically requires "EMBARGO_YYYY-MM-DD-HHMM" as a folder prefix. Verify your delivered JPGs match wire spec before upload because the embargo window is unforgiving; you cannot replace files after the release timestamp passes without manual desk intervention.

Step-by-step: prepping a wire-ready press photo

1. Start from RAW or 16-bit TIFF. The photographer's deliverable should be a high-bit-depth master, not a JPG.
2. Color-correct in ProPhoto or Adobe RGB. Edit in a wide gamut, then convert to sRGB only at export time.
3. Crop to 3:2 landscape primary. Then duplicate the file and crop to 1:1 and 16:9 variants.
4. Resize the master to 3600 pixels long edge. Use bicubic-sharper downsample.
5. Embed IPTC metadata. Headline (40 chars), Caption (full sentence), Credit, Copyright, Object Name. Photo Mechanic or Lightroom both handle this efficiently.
6. Export as JPG quality 85, sRGB. Target 4 to 6 MB per file. If oversized, push through JPG compressor with a 5 MB ceiling.
7. Verify with image info. Confirm dimensions, color space, and IPTC fields stuck. Re-export if any field was dropped.
8. Package and ship. Attach up to four crops to the pitch email; link the rest via Dropbox folder with naming convention enforced.

Common mistakes and how to fix them

• Mistake: shipping Adobe RGB JPGs to a sRGB newsroom CMS. Fix: convert to sRGB at export. Reds shift orange and skin tones go magenta otherwise.
• Mistake: missing IPTC credit field. Fix: populate Credit, Copyright, Caption before export. Wire auto-triage rejects unattributed photos.
• Mistake: 20+ MB attachments. Fix: run through JPG compressor with 5 MB target before attaching.
• Mistake: 1200-pixel "web-sized" exports. Fix: ship 3600 pixels long edge so the desk can crop without quality loss.
• Mistake: shipping HEIC straight from iPhone. Fix: convert through HEIC to JPG for universal CMS compatibility.
• Mistake: attaching 12 photos to a single pitch email. Fix: attach 3 to 4 hero shots, link the rest via cloud folder.

Real-world examples

Patagonia's PR team standardized on 4000-pixel sRGB JPGs at quality 85 with full IPTC populated by Photo Mechanic. Their wire pickup rate jumped 35 percent after the spec change because automated triage stopped flagging their pitches. SpaceX media relations ships every launch photo at 5000 pixels long edge with embedded IPTC including launch designation, payload, and photographer credit. Major aerospace publications can republish without retyping anything. Tesla's Investor Relations shifts their quarterly product hero photos via Business Wire with a 6 MB cap and 16:9 plus 1:1 variants pre-built, so social desks at Reuters and Bloomberg can post immediately.

Spec comparison: wire vs trade vs social

Outlet type	Min pixels	Format	Max file	Color
AP Wire	2400 long edge	JPG q85+	10 MB	sRGB
Reuters Pictures	3000 long edge	JPG q85+	20 MB	sRGB
Business Wire	2000 long edge	JPG q80+	10 MB	sRGB
Trade publications	1600 long edge	JPG q80+	5 MB	sRGB
Social desk reposts	1080 long edge	JPG q80+	3 MB	sRGB
Print magazine ready	3600 long edge	JPG q90 or TIFF	50 MB (TIFF)	sRGB or Adobe RGB

Advanced tips for repeat pitchers

• Build a Photo Mechanic IPTC preset. Save your default Credit, Copyright, and Source fields so every new shoot starts fully tagged.
• Maintain a Lightroom export preset for press. 3600 long edge, sRGB, quality 85, IPTC included, metadata copyright preserved.
• Run a pre-flight script. A small Python script can validate dimensions, color space, IPTC fields, and file size across an entire pitch folder.
• Generate alt text inline. Trade publications increasingly require alt text for accessibility; pre-write it into the IPTC Description field.
• Keep a master Dropbox folder per announcement. Wire pitch emails link to "press-kit/YYYY-MM-DD" with all crops, hi-res, social variants.
• Provide a one-page PDF spec sheet. Wrap your hero shots into a one-pager with JPG to PDF for journalists who want a clean print reference.
• Refresh annually. Wire specs change quietly; recheck every January and update internal templates.

FAQ

Why did the AP wire auto-reject my photo?

Most likely cause: missing IPTC Credit or Caption fields, or file size over 10 MB. Run the JPG through image info to see what fields are populated.

Should I send TIFF or JPG to a magazine?

Send high-quality JPG (quality 90+) by default. Magazines accept TIFF for cover candidates, but most editorial workflows prefer the smaller JPG. Convert with TIFF to JPG at quality 90.

Can I attach 10 photos to a pitch?

No. Attach 3 to 4 hero shots maximum; link the rest via Dropbox or Google Drive. Email attachment caps and journalist patience are both finite.

Does DPI matter for press photos?

Not for pixel quality. DPI is a print-size hint stored in metadata. What matters is the pixel count on the long edge. Use DPI converter only to update the metadata tag if a print outlet requests a specific DPI.

What if my photo is in Adobe RGB?

Convert to sRGB at export. Most newsroom CMS systems strip embedded profiles and assume sRGB, which means Adobe RGB files render with shifted color.

How do I handle embargoed photos?

Use the wire service's FTP intake with the EMBARGO timestamp naming convention. Upload at least 24 hours before release. You cannot replace files after embargo.

Should I watermark press photos?

Generally no. Newsrooms reject watermarked photos because they can't publish branded images. Embed credit in IPTC metadata instead so the byline travels with the file.

Photographer credit and rights-of-use clauses

Most professional photographers retain copyright on commissioned shoots and grant the client a license for specific uses. Press release distribution falls under most "editorial use" clauses but often excludes commercial reuse, derivative works, or sublicensing to wire partners. Confirm in writing that your photographer's contract grants the rights you need for wire distribution before pitching; some PR teams have learned this lesson expensively when a wire-syndicated photo was used commercially by a partner publication. Embed the rights-of-use note in IPTC's Rights Usage Terms field so downstream republishers see the constraint.

Multi-language caption strategy

Global product launches and international announcements often require pitches in multiple languages: English for AP/Reuters, French for AFP, German for dpa, Spanish for EFE, Japanese for Kyodo. Maintain language-specific IPTC caption versions of the same hero photo so each regional wire receives properly-localized metadata. The image content stays identical; only the embedded text fields differ. Build language variants as derivative JPGs at delivery time rather than baking into masters; the same photo serves multiple regions without duplicate captures.

Building a permanent press-kit landing page

Wire pitches benefit from a permanent press-kit URL where journalists can self-serve hi-res assets. Host a simple landing page at example.com/press with: a one-paragraph company description, founder bios with hi-res headshots, product hero photography at three crops each (3:2, 1:1, 16:9), brand logo as both rasterized JPG and vector SVG, and a downloadable PDF media kit assembled via JPG to PDF. Update the page quarterly. Journalists writing on deadline grab assets from press pages routinely; if your page is incomplete or out of date, they use the wire's stock photo of your CEO from 2019 instead of the new one you just shot.

International wire considerations

European wire services (AFP, dpa, EFE, ANSA) have slightly different photo expectations than US wires. AFP prefers 3500 pixels long edge minimum and explicit caption text in French if pitching to French-language outlets. dpa's German-language pitches expect the IPTC Headline field translated. Reuters Asia and Bloomberg Asia push toward shorter captions optimized for mobile-first publication. Maintain a wire-service spec sheet that distinguishes regional preferences; a pitch tuned to AP doesn't automatically work for AFP. Use image info to confirm character encoding on translated IPTC fields, since some Latin-1 vs UTF-8 mismatches break ingest at non-English newsrooms.

Crisis communications and recall photos

Crisis comms (product recall, executive departure, regulatory action) often need photos shipped to wires within an hour of statement release. Pre-stage the photo package: hi-res CEO headshot, product hero, factory exterior, all at wire spec, all with current IPTC. When the crisis breaks, the comms team isn't trying to export and tag photos under deadline pressure. Keep the pre-staged package in a private Dropbox folder labeled by year, refreshed quarterly. The companies that handle crises well have this infrastructure; the ones that fumble it are scrambling to export TIFFs at 2 AM.

Build a press kit that gets opened

The difference between a pitch that runs and one that gets ignored is often whether the desk editor has to spend two minutes resizing your photo. Ship correctly-sized JPGs with full IPTC metadata, keep files under the 10 MB inbox ceiling using JPG compressor, convert studio TIFF masters cleanly with TIFF to JPG, and verify metadata before sending using image info. For multi-format crop packages, lean on the aspect ratio calculator and wrap journalist-ready reference sheets through JPG to PDF. Newsrooms reward PR teams that respect their workflow, and your campaign coverage will reflect it.