Press Release Photo Specs: Size, Format and Captions
%20(1)%201.png){kind=small}
.png)
.png)
October 7, 2026
%20(1).jpg)
For internal communications, we recommend a mix of employee-generated images for authenticity, curated stock for speed, and commissioned on-site shoots for high-stakes narratives. A quick newsletter or Slack update calls for free or paid stock; a recruiting page, leadership announcement, or major event deserves a planned shoot. This piece covers licensing, image-bank workflow, and optimization next.
TL;DR:
- Building an internal image bank requires proper consent logging, tagging metadata, and regular review to ensure legal and ethical use.
- Stock photos are quick but often staged or licensed restrictively, while employee-generated images offer authenticity and stronger engagement.
- Opt for commissioning on-site shoots for major launches or leadership announcements to ensure high-quality, versatile visuals.
- Different communication channels demand specific image specs, formats, and alt text to optimize accessibility, load time, and visual impact.
- Using employee photos effectively involves diverse representation, ongoing consent management, and incorporating authentic moments to boost morale.
Every comms team ends up choosing between four sources, and each one trades speed against authenticity and cost.
Paid stock libraries give you consistent, high-resolution assets with clear licensing terms attached to the purchase. They work well when you need a polished image fast and don’t have a specific employee or location to feature, like a generic “team collaboration” shot for a policy update. The tradeoff is that paid stock photos tend to look staged, and employees notice when a newsletter features models who clearly don’t work there.
Free stock resources solve the budget problem but introduce licensing risk. Many platforms attach Creative Commons or custom licenses that restrict commercial use, require attribution, or exclude certain contexts entirely. According to Poppulo’s guidance on employee newsletters, comms teams should build an image bank from free and paid resources but always verify license terms before publishing, since an ambiguous Creative Commons claim is not the same as a cleared license.
Employee-generated content is the strongest tool for authenticity. A candid photo from a real team lunch or a hybrid standup resonates more than a polished stock image because colleagues recognize themselves and each other. The basic consent consideration here is simple: ask before you publish, and document that you asked.
Commissioned on-site shoots make sense for recruiting pages, board announcements, product launches, and major events, where the visual has to carry weight for months or years. These shoots produce a library of usable images rather than a single photo, which spreads the cost across multiple channels.
When searching for the right internal scene, specific keyword phrasing saves time:
A functional image bank starts with a workflow, not a folder. The process runs in four steps: capture the image, log consent, attach metadata, and store it in a searchable system.
Consent should not be a single checkbox. Rutgers Communications recommends treating consent as tiered: internal-only use, owned external use (website, social), and paid or long-life use (advertising, print campaigns that run for years). A general release signed at hiring often does not cover future external or paid uses, so the safest approach stores consent entries by asset, with a timestamp and the exact scope granted, in a secure, auditable log rather than relying on verbal clearance.
A simple tagging taxonomy keeps the bank usable as it grows: event name, role or department, campaign tag, file format, and license tier. Retention policy matters too: set a review date for employee photos so departed staff aren’t still featured in recruiting materials years later.
Photo contests and event galleries are popular engagement tools, but they create exposure if entries aren’t cleared. Require a simple submission consent at the point of entry, before any image enters the public gallery or newsletter.
Pro Tip: Attach consent tier directly in the file name or metadata field, so anyone pulling an image later can see the permission scope without digging through a separate log.
Copyright protection doesn’t stop at your office door. An image used only on your intranet or in a Slack channel is still a publication, and the photographer or stock agency retains rights unless the license says otherwise.
When you pull a stock photo, read the license for its intended scope. Many stock licenses distinguish internal use (training materials, intranet, internal newsletters) from external use (advertising, press releases, public social media), and using an internal-only license for a recruiting campaign violates the terms even if no one objects right away.
Employee releases need specific elements to hold up: the employee’s name, the scope of channels where the image can appear, the duration of use, and whether any paid or promotional use is included. A release that only says “for company use” leaves too much open to interpretation.
Watch for these red flags before publishing:
The mitigation is always the same: verify the license or release before the image goes live, not after a complaint arrives.
Different channels demand different specs. An intranet hero image usually needs at least 1920 by 1080 pixels to stay crisp on a widescreen monitor, while an email header works the best closer to 600 pixels wide to avoid slow loading. Square crops (1080 by 1080) serve social feeds, and thumbnail previews for an intranet feed can run smaller, around 400 by 400.
File format matters as much as size. JPEG remains the standard for photographs because it balances quality and file size well; PNG is better reserved for graphics with transparency. Compressing images before upload keeps page load times fast, which matters because visual content measurably increases engagement in employee newsletters, an advantage that disappears if a slow-loading image gets skipped before it renders.
Alt text isn’t optional. Every image needs a short, descriptive phrase (not just “team photo”) so screen reader users get the same information as sighted readers.
Quick accessibility checklist:
Choose shots that show real variation in roles, ages, and settings, like a warehouse floor next to an executive meeting, to signal that the comms feed reflects the whole organization rather than one department.
Before any shoot, a short visual planning session between the writer, the photographer, and the comms lead changes the outcome more than equipment or budget does. Ragan Communications’ reporting on Yale’s intranet describes exactly this: a brief discussion covering what the image should make employees understand, what makes the moment specific to that workplace, and whether the story needs a person, a place, or a moment captured. That same framework works whether you’re planning a single photo or a full-day shoot.
We prioritize three things in every session: authentic interactions over staged poses, planning each shot for multiple uses (recruiting, intranet, social) rather than one deliverable, and fast turnaround so the content publishes while the story is still relevant. A leadership announcement or office opening typically justifies booking a production partner when the images need to hold up across a recruiting page, an investor update, and a press release at once.
Representation in internal photography should reflect who actually works at the organization, not a narrow slice of it. That means featuring people across departments, not just the leadership team or the marketing department, since those tend to get photographed most often by default.
Rotate who appears in your image bank regularly. If the same five employees show up in every newsletter, the content starts to feel exclusive rather than representative, even without anyone intending that result.
Capture a range of roles and settings: warehouse and field staff alongside office workers, remote employees on video calls alongside in-person teams. A company with multiple office locations should make sure every location appears in the rotation, not just headquarters.
Avoid staged diversity, where people are visibly posed to check a demographic box. Candid moments during real meetings or events tend to read as more authentic than arranged group shots, and employees can usually tell the difference.
Finally, ask before assuming someone represents a category they haven’t claimed. Respect how individuals describe themselves rather than labeling them in captions or tags.
Not every moment belongs in a photo, and not every employee wants to be photographed. Build an easy way for staff to opt out of being included in internal photography, whether that’s a sticker on a badge, a note in the employee directory, or a simple form submitted to HR.
Be careful with photos taken during sensitive moments: layoffs, medical leave announcements, disciplinary meetings, or personal milestones an employee hasn’t chosen to share publicly. These situations call for no photography at all, regardless of how good the lighting looks.
When a photo includes identifiable faces, confirm that everyone in frame has given permission for that specific use, not just a general one from months earlier. A group shot from a team event can include someone who left the company since, and continuing to feature them without updated consent creates unnecessary risk.
Store any personal details tied to a photo, like a health accommodation visible in frame, with the same care as other sensitive HR data. When in doubt about whether an image crosses a privacy line, leave it out of the publication and ask the people in it directly.
Photos work best when employees see themselves and their actual colleagues in the content, not generic stand-ins. Ragan Communications reports that visuals showing real colleagues and imperfect workplace moments outperform generic stock because people recognize faces and places they know.
A few tactics make this easier to sustain. Running a monthly photo contest around a theme (favorite workspace, team lunch, remote setup) gives employees a reason to submit their own images, which also feeds the image bank with authentic content. Featuring employee photos in recognition posts, rather than stock graphics, ties visual content directly to morale-building moments like work anniversaries or project completions.
Pairing photos with short captions that name the people and the context (rather than a vague “team collaboration”) gives the image more weight. A caption that says who’s in the photo and what they accomplished turns a picture into a small story.
Rotating photo ownership across departments, instead of always pulling from the same handful of contributors, keeps the content feeling current and reduces the sense that only certain teams get visual attention.
Most comms teams need three categories of tools: a digital asset manager, basic editing software, and a consent-tracking system.
A digital asset manager, even a modestly priced one, solves the “where did that photo go” problem by centralizing storage with searchable tags. Pairing this with a shared drive structure organized by the tagging taxonomy covered earlier keeps things simple without requiring a dedicated IT project.
For editing, lightweight tools handle most internal communication needs without a full design team. Canva and Adobe Express both offer cropping, resizing, and basic retouching suited to non-designers on a comms team, while Adobe Lightroom suits teams doing heavier photo editing from a commissioned shoot.
Consent tracking can live in something as simple as a shared spreadsheet with locked edit permissions, as long as it’s treated as a system of record rather than an afterthought. The goal is the same regardless of tool: every asset should be findable, properly licensed, and ready to drop into the next newsletter or intranet post without a last-minute scramble to confirm it’s clear to use.
The clearest signal of whether photography is working comes from engagement metrics already available on most internal platforms: open rates and click-throughs on newsletters, time spent on intranet pages, and reaction or comment counts on posts that include employee photos versus those that don’t.
Comparing a photo-led post to a text-only version of the same announcement, sent to similar audiences, gives a rough read on whether the image moved the needle. Poppulo’s research on employee newsletters points to images and visual communication as a meaningful driver of engagement in this content, which supports tracking these comparisons consistently rather than assuming photos help without checking.
Qualitative feedback matters too. A short pulse survey asking employees whether they feel represented in internal content, or whether recent photos felt authentic, surfaces issues that click-through rates won’t show, like whether the same few people keep appearing or whether certain departments feel invisible.
The conventional advice treats stock photography and employee-generated content as competitors, pick one lane and stick with it. That framing misses the point. The real failure mode isn’t choosing the wrong source category, it’s skipping the consent and tagging work because it feels like overhead rather than the actual deliverable.
Most comms teams invest their effort in finding or shooting the image and treat licensing as a formality to clear later. That ordering is backwards. A photo with no documented consent or an ambiguous license is a liability sitting in your drive, regardless of how good it looks in the newsletter.
If you do one thing differently after reading this, build the consent log before you build the photo library. The image bank is only as useful as the permissions attached to it, and a well-tagged, properly cleared set of twenty photos beats an untracked folder of two hundred every time.
— Kevin
When a moment is too important to risk on stock photography, we bring the shoot to you. Our START UP service covers team and leadership headshots for recruiting pages and announcements. STANDARD and ENTERPRISE branding photography support multi-location programs that need consistent imagery across offices. NETWORKING, SUMMIT, and CONFERENCE event coverage turns a single gathering into a library of internal and external content.
Every shoot starts with a short discovery conversation, similar to the planning session described above, so the images serve recruiting, intranet, and leadership communications at once. Book a shoot through our headshots page to get a turnaround timeline for your next launch or event.
Internal communications teams manage the messages, channels, and content that keep employees informed and connected to company goals, from newsletters and intranet posts to leadership announcements. Photography is one tool within that broader function, used to make messages more engaging and relatable.
Compensation for internal communications roles varies widely by seniority, industry, and location, and is not something we track or report on. Checking a dedicated salary resource or job listing for your specific market and role level gives a more accurate picture than any general estimate.
Common examples include employee newsletters, intranet posts, town hall recordings, Slack or Teams announcements, leadership videos, and recognition posts celebrating individual or team achievements. Photography and video support most of these formats by adding a human element to otherwise text-heavy updates.
Comms teams continue leaning toward authentic, employee-generated visuals over polished stock photography, paired with more structured image-bank governance to manage consent and licensing at scale. Hybrid and distributed teams also push demand for visuals that represent remote work accurately, rather than defaulting to in-office imagery alone.
