Company Headshot Guidelines: A Copy-Paste Template for HR and Brand Teams

Company headshot guidelines are a one-page written standard that tells employees exactly how their photo should look and where it goes. Done well, they take five minutes to read, remove every judgment call, and make a 200-person team page look deliberate instead of accidental. Here is the full template.

Why headshot consistency is a brand problem, not a vanity problem

Nobody notices a consistent set of team photos. They notice an inconsistent one. A grid where three people are cropped at the chest, two at the waist, one is outdoors at golden hour and one is clearly a cropped wedding photo reads as a company that doesn't sweat details — which is exactly the wrong signal on an About page a prospect visits before a first call.

The practical cost is not aesthetic, it's operational. Without a written standard, every new hire generates the same three questions to HR, every rebrand triggers a scramble, and the marketing team ends up manually retouching backgrounds the night before a website launch. A guideline document converts a recurring judgment call into a one-time decision.

• About and team pages — where mismatched crops and backgrounds are most visible, because photos sit side by side in a grid
• LinkedIn profiles — where employees represent the company individually, and where you can recommend but not enforce
• Sales decks and proposals — where a pod of four faces appears on one slide and any mismatch is obvious at 20 feet
• Internal tools — Slack, the HRIS, the intranet directory, video call profiles
• Press, conference and speaker submissions — where organizers ask for a high-resolution file on a two-day deadline

It's worth being clear-eyed about the size of the effect. A consistent team page will not close a deal on its own, and no serious buyer picks a vendor because the headshots matched. What it does is remove a small, avoidable signal of carelessness from a page that is often the second or third one a stranger looks at, and remove a recurring administrative chore from three different teams. That is a good enough reason on its own.

Decide who owns the standard before you write it

A headshot standard with no owner becomes a suggestion within one quarter. Before drafting anything, name one person with final approval authority — usually in brand, marketing ops or people ops — and one shared inbox or channel where photos get submitted. Everything else in the document is downstream of that single decision.

• Owner — one named person who approves or rejects submissions, not a committee
• Submission route — a form, a shared drive folder, or an HRIS upload field; pick one and kill the others
• Turnaround SLA — commit to something small like three business days, so people don't chase
• Escalation path — what happens when someone declines to be photographed at all

Language matters more than most drafts assume. "Please consider a solid-color top" reads as optional and will be ignored by roughly half your team. "Solid-color tops are required; patterns and visible logos will be sent back" reads as a standard. Write requirements as requirements and preferences as preferences, and be honest about which is which.

The eight decisions to standardize

Almost every question employees ask about company photos maps to one of eight decisions. Make each one explicitly, write the answer in a single sentence, and your guideline document is essentially finished. The rest is formatting and examples. Work through them in order, because the earlier choices constrain the later ones.

1. Background

Pick one background and one fallback. The safest default for a team grid is a plain, evenly lit neutral — light grey, off-white, or a soft mid-tone — because it survives cropping, resizing and being placed next to any brand color. Environmental office backgrounds photograph beautifully in isolation and fall apart in a grid, because no two desks look alike. If you want warmth, standardize a single blurred office wall rather than "wherever you happen to be sitting." Our guide to headshot backgrounds covers the trade-offs by use case.

2. Framing and crop

Framing is the single biggest source of visual chaos in team pages, and it costs nothing to fix. Specify where the crop starts and stops in plain language: head-and-shoulders, top of frame roughly a quarter-head above the hairline, bottom of frame at mid-chest, eyes on the upper third. Also specify how much the subject fills the frame — if one person's head occupies 60% of the image height and the next occupies 25%, the grid will look wrong even with identical backgrounds.

3. Outfit palette

Don't dictate a uniform. Dictate a palette and a texture rule. Solid, mid-to-dark tones photograph consistently across skin tones and lighting setups; tight patterns can create moiré on screens; visible logos date the photo the moment the brand or sponsor changes. A workable rule for most companies is: solid colors, no visible logos or slogans, layers welcome, one notch above daily office dress. Point employees at a fuller explanation like what to wear for a headshot instead of writing three paragraphs of wardrobe advice into your policy.

4. Expression and posture

Expression is where guidelines usually get vague and unhelpful. Rather than "look approachable," define a range and let people pick within it: a genuine closed-mouth or open smile, eyes to camera, shoulders angled slightly off-axis, chin forward and slightly down. Then state the outliers you'll reject — sunglasses, hats that shadow the eyes, arms crossed, and anything shot from below eye level. If your culture is genuinely more informal, say so, but say it once and consistently.

5. Aspect ratio and orientation

Standardize on a square master file. A 1:1 crop survives being displayed as a circle on LinkedIn, a rounded square in Slack, and a square or 4:5 card on a website with minimal loss. If your website design uses a portrait card, ask for a square master plus generous headroom so a 4:5 crop can be derived without cutting the top of anyone's head. One master ratio, derived crops — never the reverse.

6. File specs and naming

Specify the master file once, then let each destination be a derivative. Ask for the largest usable original and store it; compress at the point of publication, not at the point of collection. A naming convention that sorts predictably saves your web team an afternoon every launch.

• Master file — square, at least 2000 × 2000 px, JPEG at high quality or the untouched original, sRGB color
• Web derivative — export at roughly twice the displayed size for high-density screens, then compress; Google's own compression study found lossy WebP files run 25–34% smaller than JPEG at an equivalent quality score
• Page weight — a widely used performance target is keeping individual images under about 200 KB, which is trivial for a 400 px team thumbnail
• Naming — lastname-firstname-headshot-YYYY.jpg, so files sort alphabetically and the vintage is visible without opening anything

7. Update cadence

Put a number in the document or it will never happen. Photographers and HR guides converge on refreshing corporate headshots roughly every one to three years, with client-facing leadership at the shorter end. More useful than a calendar rule are the event triggers: a role change, a meaningful appearance change, a rebrand, or any photo that no longer looks like the person who walks into the meeting. A rolling model — tied to onboarding and annual review cycles — is far easier to sustain than a company-wide reshoot every third year.

8. Where the photos live

Name the single source of truth and the list of destinations it feeds. Most companies discover during a website rebuild that the only copy of a departed executive's headshot is in someone's downloads folder. A shared drive folder with per-person subfolders is enough; a proper DAM is better if you already have one. Then list every destination explicitly — website, HRIS, Slack, email signature, sales deck template, press kit — so nobody has to guess where else the photo needs to be updated.

Where each platform will crop your photo

Guidelines fail when they ignore how images are actually displayed. Every destination crops, compresses and reshapes differently, and a standard that produces one good master file for all of them is worth writing down. These are the specs that matter as of 2026, checked against the platforms' own documentation.

• LinkedIn profile photo — 1:1 ratio, minimum 400 × 400 px, maximum file size 8 MB, and always displayed as a circle. Upload at 800 × 800 px or larger so LinkedIn's compression has room to work. Full specs live in our LinkedIn photo size reference.
• Slack — minimum 512 × 512 px, maximum 1024 × 1024 px, 1 MB file size cap, JPG, PNG, GIF or BMP, displayed as a rounded square.
• Website team grid — measure the actual rendered container first; team thumbnails are often far smaller than people assume. Export at 2× that size for high-density screens and compress hard.
• Email signatures and HRIS — usually the smallest render of all, often 80–150 px, and frequently the one nobody updates. Generate it from the same master rather than letting people crop their own.
• Decks and press — keep the uncompressed master available. Conference organizers routinely ask for print-resolution files at short notice, and a 400 px web thumbnail won't do.

The circle crop deserves special mention because it silently breaks otherwise good photos. Anything in the corners of a square image — a shoulder, an elbow, part of a logo on a wall — disappears on LinkedIn and Slack. Center the face, leave a little breathing room, and check the master in a circular mask before approving it.

The copy-paste company headshot guidelines template

Below is a complete, adaptable guideline block. Replace the bracketed fields, delete anything that doesn't apply to your company, and publish it wherever your team actually reads things — the handbook, the onboarding checklist, the brand hub. It's intentionally short; long photo policies don't get read.

Purpose and scope

These guidelines define the standard for employee headshots at [COMPANY]. They apply to every photo used on our website, in client-facing materials, and in internal tools. They are a strong recommendation — not a requirement — for personal LinkedIn profiles. Questions and submissions go to [OWNER / CHANNEL].

The photo standard

• Background: plain [light grey / off-white / brand neutral], evenly lit, no visible objects, doors or windows.
• Framing: head and shoulders. Crop just above the hairline at the top and at mid-chest at the bottom. Eyes on the upper third of the frame.
• Head size: the head should fill roughly [40–50%] of the image height, so photos match when placed side by side.
• Angle: camera at eye level. Shoulders turned slightly off-axis, face toward the lens.
• Expression: a genuine smile, closed-mouth or open — your choice. Eyes to camera.
• Lighting: soft, front-dominant light. No hard shadows across the face, no backlit windows, no direct overhead office light.
• Not accepted: sunglasses, hats covering the eyes, heavy filters, group photos cropped to one person, visible logos or slogans, images below [2000 × 2000 px].

Wardrobe

• Solid colors only. Avoid tight stripes, small checks and busy prints.
• Mid-to-dark tones work best against our light background.
• No visible brand logos, event badges or slogans.
• Dress one notch above your usual workday standard for your role.
• Layers — a blazer, jacket or structured knit — read as more polished on camera than a single loose top.

Files and delivery

• Submit a square (1:1) file, at least [2000 × 2000 px], JPEG, sRGB.
• Name the file lastname-firstname-headshot-YYYY.jpg.
• Upload to [FOLDER / FORM]. Do not email photos or send them in chat.
• [OWNER] reviews within [3] business days and either approves or requests a reshoot with a specific reason.
• [COMPANY] produces the web, Slack and deck versions from your master file. Please don't pre-crop or pre-compress.

Refresh, changes and offboarding

• Refresh your headshot every [2] years.
• Refresh immediately after a promotion or role change that appears on the website.
• Refresh after any significant change in appearance — new glasses, a substantially different hairstyle, facial hair.
• New hires submit a photo within [30] days of start date, as part of onboarding.
• Photos are removed from public pages within [5] business days of a departure.

Consent and approval

• Participation in the company photo program is voluntary. If you prefer not to have a public photo, tell [OWNER] and we'll use a placeholder — there is no consequence for declining.
• By submitting a photo you agree to its use on [LIST OF DESTINATIONS]. You can withdraw that permission at any time, in writing, for future uses.
• [OWNER] holds final approval. If your photo is declined, you'll be told exactly what to change.
• Exceptions for religious dress, medical reasons or personal safety are granted on request, no explanation required.

Consent, opt-outs and offboarding

This is the part most photo guidelines skip and later regret. Under the EU and UK GDPR, consent must be freely given, specific, informed and unambiguous. A blanket line in an employment contract saying "you consent to photos" is generally not sufficient, and regulators have repeatedly flagged that the power imbalance between employer and employee makes consent harder to rely on in the workplace than most drafts assume.

US employers face a looser federal picture but not a blank check. A number of states have right-of-publicity statutes covering commercial use of a person's likeness, and Illinois, Texas and Washington regulate biometric identifiers specifically. The practical implications below are worth building into your process rather than bolting on later. None of this requires a legal team to implement, though a lawyer should review your final wording if you operate across multiple jurisdictions.

• Make declining genuinely costless. Have a placeholder or initials avatar ready so an opt-out doesn't stand out as a gap.
• Be specific about destinations. "Website, LinkedIn company page, sales materials and recruiting content" is informed consent; "marketing purposes" is not.
• Allow withdrawal. Consent can be revoked for future uses, even if you can't recall a printed brochure already distributed.
• Define an offboarding SLA. Photos of former employees lingering on an About page for six months is both a bad look and a data hygiene problem.
• Keep a record. A dated row in a spreadsheet showing who consented, to what, and when is usually enough.

How to actually produce the photos

A standard is only useful if there's a realistic way to meet it. The right production route depends less on budget than on geography: a single-office company and a fifteen-city distributed team have genuinely different problems, and the second one is where most guideline documents quietly collapse. Three routes cover almost every case.

On-site photographer

For a co-located team, booking a photographer for a day is still the highest-ceiling option. One lighting setup, one background, one person directing expression — consistency comes free, and a good photographer will coax a usable expression out of people who hate being photographed. Published 2026 rates for on-site team days span roughly $75–$300 per person, falling as headcount rises, or a flat rate that commonly runs from about $1,500 for a short in-office session up to $6,000 for a full day in a major market. The weaknesses are scheduling, absentees, and the new hire who joins three weeks after the shoot and never matches. Our headshot price benchmark breaks the numbers down by format.

AI-generated headshots

AI headshot tools solve the distributed-team problem directly: every person submits selfies from wherever they are and gets studio-style results against whatever background you've standardized, without a travel budget. They're also fast enough to onboard a new hire the week they start. Be honest about the limits, though — AI output can drift from a person's actual likeness, results vary meaningfully between individuals, and some faces, skin tones, hairstyles and glasses reproduce less reliably than others. A photographer can also be directed in real time; an AI tool cannot. Always let the subject approve their own photo, and always treat "does this look like me?" as the pass/fail test rather than "is this flattering?"

Self-shot photos with a written recipe

For small or budget-constrained teams, a disciplined phone shoot is a legitimate third option, and better than a grid of mismatched old photos. It only works if you replace judgment with a recipe: same wall color, subject about three feet off the wall, window light to one side and slightly in front, phone at eye level on a stack of books, rear camera, portrait mode off, a colleague pressing the shutter. Expect a lower ceiling and more rejected submissions, and budget your reviewer's time accordingly.

The hybrid most teams land on

In practice, many companies run a photographer day for leadership and anyone whose face appears in sales situations, and use a faster route for everyone else and for rolling new-hire updates. That works as long as the guideline document — not the production method — defines the look, so photos from both sources land on the same background, crop and palette. We covered the logistics of this in more depth in our piece on team headshots for remote teams.

Rolling it out without a three-week email thread

Publishing the document is the easy half. Adoption is where standards live or die, and the failure pattern is predictable: a long announcement, no examples, no deadline, and a submission process with three possible routes. Run it like a small project instead, with a pilot, a date and a single owner.

1. 1Ship examples with the text. Three approved photos and two rejected ones (with the reason) teach more than 500 words of specification.
2. 2Pilot with one team. Ten people will surface every ambiguity in your draft before you send it to 200.
3. 3Set one deadline and one channel. A four-week window and a single upload link beats an open-ended request every time.
4. 4Let people choose their own photo. Approval anxiety is a common reason employees stall; giving them the final say removes most of it.
5. 5Attach it to onboarding. Once the headshot step is a checklist item on day one, the standard maintains itself.
6. 6Re-audit annually. Sort the master folder by year in the filename and you'll spot stale photos in seconds.

Five ways headshot standards quietly fail

Most broken photo grids aren't caused by a bad guideline document. They're caused by a good one that nobody maintained. These are the failure modes worth designing against from the start, because each of them takes months to become visible and an afternoon to prevent.

• No named owner. Submissions land in a general inbox, nobody approves, standards drift back to whatever people had.
• Preferences written as requirements, or vice versa. If everything is "recommended," nothing is; if everything is mandatory, you'll be denying exceptions you should have granted.
• No master files. Only the compressed web versions were kept, and the next site redesign needs images at twice the resolution.
• New hires exempted by accident. The standard was a one-time project rather than an onboarding step, so it decays by one person per hire.
• Enforcing on LinkedIn. Personal profiles aren't company property. Recommend, provide the assets, and leave it there — insisting creates friction with no upside.

A workable company headshot guideline fits on one page, names one owner, defines eight things, and links out for the details. Everything beyond that is optional polish. If you write the document today and attach it to your onboarding checklist tomorrow, the team page takes care of itself for the next two years.