Yes, a team's headshots should match across LinkedIn, the company website, and directory listings, but matching does not mean the identical cropped file in three places. It means one master photograph per person, exported to each platform's own specification and replaced everywhere at the same time. Each platform crops differently: LinkedIn shows a circle, a website team page is usually a square or a portrait rectangle, and directories set their own sizes. Across more than 800 Canadian organizations BusinessPortraits.ca has photographed since 2017, the teams whose galleries still look like one company are the ones that treat every platform placement as a crop of one master file, not a separate photo.
You commissioned headshots for the team, or you are about to. Now the photos have to go somewhere: the company website team page, every employee's LinkedIn profile, the firm's entry in a few directories. Do they all need to match, and how do you handle the fact that LinkedIn crops a photo into a circle while your website wants a rectangle?
This post is for the person who owns that problem, usually a marketing, brand, or HR lead at a law firm, accounting practice, tech company, or enterprise. It assumes you already have, or are commissioning, a consistent set of headshots. The job here is deployment: getting one set of photos onto every platform so the team reads as one company.
Five things decide how that works:
- Matching is not optional, but "match" has a precise meaning: one recognizable identity per person and one visual system across the team, not one identical file pasted everywhere.
- Matching is a single-source standard: one master photograph per person, exported to each platform's specification.
- Each platform has its own specification, and they differ. The table below covers LinkedIn, your website, directories, email signatures, and video calls.
- Mismatches happen in predictable ways, and they carry a real cost in recognition and trust.
- Staying consistent is a governance question: one owner, one update cycle, and new hires added before the gap shows.
Should your team's headshots match across LinkedIn, your website, and directories?
They should. A prospective client, candidate, or partner rarely meets your team in one place. They find a partner on the website, open that person's LinkedIn profile in a second tab, and may cross-check a directory listing before a first conversation. When those images match, the viewer registers one professional. When they do not, the brain has to reconcile what look like different people.
That reaction is fast and involuntary. In a foundational experiment, Princeton researchers Janine Willis and Alexander Todorov found that people form judgments of trustworthiness and competence from an unfamiliar face after an exposure of just 100 milliseconds, and that those judgments barely shift when the viewer is given unlimited time. The headshot is doing its work before a word of the bio is read.
It is not doing that work in one place. The typical professional now appears across roughly six to seven platforms: a website bio, LinkedIn, an email signature, a workplace chat and video-call profile, a conference speaker bio, one or more directories. Each is a separate decision about which photo to use and how to crop it, and left alone, those decisions drift apart.
What matching actually means: the single-source rule
Matching does not mean the same identical file everywhere. It cannot, because platforms crop differently. It means one master photograph per person, captured in one session, then exported into the crop and size each platform requires.
Across more than 800 Canadian organizations BusinessPortraits.ca has photographed since 2017, the headshots that still look like one company across LinkedIn, a website, and a directory are never three separate photos. They are one master file per person, exported to each platform's specification and replaced everywhere on the same day. We call it the single-source rule: photograph once, crop many, update everywhere together.
One master, three exports.
Fig. 1 · Single-source rule, in practice
Master
Producing that master file, with consistent lighting and background across a whole team, is its own piece of work, especially for a team spread across locations.
What stays fixed across every platform, and what is allowed to change
Three constants.
- PhotographThe same capture, of the same person, from the same session.
- TreatmentBackground, lighting, and retouching, reading as one studio's work across the team.
- CurrencyEvery surface carries the current photo. They change together.
One variable.
- Crop ratioPlatform decision. Square, circle, or 4:5; follow each platform's spec.
- Pixel sizeExport to each platform's recommended dimensions.
- File formatJPEG vs PNG vs WebP as each platform requires.
Changing the frame is correct and necessary. Changing the photograph is what breaks consistency.
The platform-by-platform specification table
Here is what each surface needs. These specifications are current as of May 2026; platforms revise dimensions and limits periodically, so confirm the current numbers before a team-wide rollout.
| Platform | How it displays | Crop to supply | Recommended size | The main gotcha |
|---|---|---|---|---|
| LinkedIn personal profile | Circle | Square · 1:1 | 640 × 640 px or larger 400 × 400 px min · ≤ 8 MB |
The circular mask trims the corners; a crop framed tight for a square loses the top of the head. |
| Company website team page | Varies by theme Usually square or 4:5 |
Square or 4:5 | 600 × 600 to 1200 × 1200 px Upload at ~2× display size |
The site template controls the final crop; supply a generous master and let it crop. |
| External directory or association listing | Set by each directory Often a small square |
Square · 1:1 · medium | Directory-specified Often 300 × 300 to 500 × 500 px |
Every directory differs and many compress hard, and this is the surface most likely to hold an old photo. |
| Email signature | Small fixed square | Square · 1:1 · tight | 100 × 100 to 200 × 200 px Supply at 2× |
At small sizes a tight head-and-shoulders crop reads better than a wide one. |
| Workplace chat and video-call profile · Teams, Slack, Zoom | Small circle or rounded square | Square · 1:1 | Platform-specified Often 200 × 200 px or larger |
Shows on every chat message and mention, not only when the camera is off in a call; an old or casual photo here undercuts a polished website. |
-
01 LinkedIn personal profile
- Displays
- Circle
- Supply
- Square · 1:1
- Size
-
640 × 640 px or larger
400 × 400 px min · ≤ 8 MB
The circular mask trims the corners; a crop framed tight for a square loses the top of the head.
-
02 Company website team page
- Displays
- Varies by theme, usually square or 4:5
- Supply
- Square or 4:5
- Size
-
600 × 600 to 1200 × 1200 px
Upload at ~2× display size
The site template controls the final crop; supply a generous master and let it crop.
-
03 External directory or association listing
- Displays
- Set by each directory, often a small square
- Supply
- Square · 1:1 · medium
- Size
-
Directory-specified
Often 300 × 300 to 500 × 500 px
Every directory differs and many compress hard, and this is the surface most likely to hold an old photo.
-
04 Email signature
- Displays
- Small fixed square
- Supply
- Square · 1:1 · tight
- Size
-
100 × 100 to 200 × 200 px
Supply at 2×
At small sizes a tight head-and-shoulders crop reads better than a wide one.
-
05 Workplace chat and video-call profile · Teams, Slack, Zoom
- Displays
- Small circle or rounded square
- Supply
- Square · 1:1
- Size
-
Platform-specified
Often 200 × 200 px or larger
Shows on every chat message and mention, not only when the camera is off in a call; an old or casual photo here undercuts a polished website.
One principle runs through the whole table: supply every platform a generous, high-resolution square master and let the platform crop. Pre-cropping a file tight for one platform and reusing it everywhere is what produces clipped foreheads and off-center faces.
LinkedIn: a square photo shown as a circle
LinkedIn is where most buyers verify a person. It accepts a square image and, per LinkedIn's own image specifications, wants at least 400 by 400 pixels, then displays that square inside a circle. A head-and-shoulders crop composed to fill a square corner to corner loses its corners to the mask, which can clip the top of the head. Compose the LinkedIn crop with the face centered and a little breathing room.
LinkedIn's own data indicates a member with a profile photo receives up to 21 times more profile views and 9 times more connection requests than one without. That is LinkedIn describing its own platform, so read it as a platform incentive, but the direction is not in dispute.
Your website team page: the design controls the crop
A company website is the surface you control most and specify least precisely, because the crop is set by the theme. Some templates use a square, some a 4:5 portrait, some a wide landscape card. Hand the website a high-resolution square master, between 600 × 600 and 1200 × 1200 pixels, uploaded at roughly twice the display size, and let the content management system crop. A generous master survives a template change; a tight crop does not.
External directories, listings, and event speaker pages
Directories are the quiet failure point. Legal directories, accounting bodies, association member listings, conference and event speaker bios, partner and board pages elsewhere: each sets its own dimensions and compresses on its own terms. Buyers use them to verify your team independently, and they are the surface most likely to show a headshot two versions out of date, because no one inside the company owns them. When a partner speaks at an industry event, the organizer's speaker page is one more place the headshot has to match. Put these listings on the same master file and update cycle as everything else.
The proof: one studio, one setup, every hire
Why platform mismatches happen, and what they cost you
Mismatches are rarely a decision. They accumulate. Someone joins and adds a phone selfie to the team page "for now." A partner updates LinkedIn with a conference photo and never touches the website. A rebrand refreshes the website but skips the directories. None of it is a choice to look inconsistent. It is the absence of a system.
Recognition cost
The first cost is literal: people may not recognize that two photos are the same person. In a study published in the journal Cognition, Jenkins, White, Van Montfort, and Burton showed that within-person variation in everyday photographs is large enough that viewers unfamiliar with a face sorted multiple photos of one person into separate identities. For a buyer cross-referencing your team, a mismatch is not a styling preference. Two different photos can read as two different people.
Source · Jenkins, White, Van Montfort & Burton · Cognition, 2011
Trust cost
The second cost is trust, and it lands on the company. Consistency is a recognized driver of brand trust: research in the Journal of World Business found that brand consistency and congruency foster brand trust, which in turn supports growth. A team's headshots are one of the most visible consistency signals a company has, because faces are what people look at first.
Source · Eggers et al. · Journal of World Business, 2013
This compounds because buyers now check alone. Gartner reports that 67 percent of B2B buyers prefer a rep-free buying experience, researching independently across digital channels before they contact a vendor. The team they evaluate is the team as it appears online, across every platform at once. A survey of brand professionals by Lucidpress, now Marq, linked consistent brand presentation across channels to revenue up to 33 percent higher. Treat that as directional, but the point holds: visual coherence is not cosmetic.
How to keep every platform current: who owns it, and when to update
A headshot is not finished when the photographer delivers the file. It is finished when every platform shows it. Treating delivery as the finish line is how the directory listing ends up three years stale. The currency rule is simple: when the photo changes, every surface changes, on the same day.
Give the standard one owner
The most common reason teams drift is that no one owns the standard. "Everyone keeps their own profile updated" guarantees drift, because individuals crop, filter, and re-shoot on their own schedules. Assign one owner, usually marketing or brand, who holds the master files and the specification and treats every placement as a controlled export, with HR feeding in new hires. The cadence for refreshing the whole team is its own decision, covered in our guide to how often to refresh team headshots.
Add new hires before the gap shows
A team gallery degrades fastest at the seams, and the seam is the new hire photographed late. A headshot booked into the first 30 days of onboarding, against the same documented setup, joins the gallery as a true match. A headshot deferred to "the next batch" sits as a selfie for months and announces itself. For a team hiring continuously, the structural fix is an ongoing arrangement that keeps the master setup on file, so every new hire is photographed to match without anyone re-litigating lighting or background. That is the reason some firms move headshots onto a standing subscription. Either way, the input is the same: a session that produces a clean master file per person, and what a session covers is the same for one new hire or forty.
Master file as source of truth · five platform rows with live crop-spec readouts.
Echoes the spec tableFrequently asked questions
Should everyone on our team use the same headshot on LinkedIn and on the company website?
Yes, the same master photograph, exported to each platform's crop. The goal is that a client moving from your website to a team member's LinkedIn profile sees the same person, photographed the same way. The files are not byte-for-byte identical, because LinkedIn crops to a circle and most websites use a square or rectangle, but they come from one session and one master image. Different photos taken at different times are what break the effect.
Does "matching" headshots mean every photo has to look identical?
No. Matching means consistent, not identical. Every headshot should share the same background treatment, lighting, framing approach, and retouching style, and each person should still look like themselves. It does not require robotic uniformity. The one thing that must be constant is that a person's photo across platforms comes from the same master file. The crop changes per platform; the photograph does not.
What size should a headshot be for LinkedIn versus a company website?
As of May 2026, LinkedIn accepts a square image at 400 by 400 pixels minimum and displays it as a circle; 640 by 640 or larger renders sharply on modern screens. A company website team page varies by template, but a square master between 600 by 600 and 1200 by 1200 pixels covers most designs, uploaded at roughly twice the display size for high-resolution screens. Confirm both platforms' current specifications before a team-wide rollout, because they change.
Why does the same headshot look cropped or zoomed differently on each platform?
Because each platform applies its own crop. LinkedIn fits your photo into a circle and trims the corners. A website template may force a square or a 4:5 rectangle. An email signature shrinks it to a small square. If you upload one tightly cropped file everywhere, some platforms clip the face. The fix is to supply a generous, high-resolution master and let each platform crop from it, rather than pre-cropping tight.
Should we use the same headshot on external directories and association listings?
Yes. Directories such as legal directories, accounting bodies, and industry associations are part of how buyers verify your team, and they are the surface most likely to show an outdated photo because no one inside the company owns them. Use the same master file there as everywhere else, cropped to the directory's specification. When the team refreshes its headshots, directory listings belong on the update list, not in the blind spot.
How often should we update headshots across every platform?
Update every platform at the same time, whenever the photo changes. The trigger is not the calendar; it is any change: a new master photo, a promotion, a rebrand, or a new hire. Most teams refresh team-wide headshots on a defined cycle and add new hires in between. The rule that matters across platforms is synchronization: when one surface updates, all of them update, so the team never drifts out of alignment.
Who should own keeping the team's headshots consistent: HR, marketing, or each employee?
One owner, usually marketing or brand, with HR feeding in new hires. Leaving each employee to manage their own profile photo guarantees drift, because individuals crop, filter, and update on their own schedules. A single owner holds the master files and the platform specification, and treats every placement as a controlled export. That is the difference between a team page that holds together for years and one that fragments within a year.
Can we use an AI-generated headshot to fill a gap on the team page?
The question behind this one is whether any stand-in can fill a missing person's spot, and the test is the same for every option. The single-source standard is a photograph captured to your documented setup: the same background, lighting, and framing as the rest of the team. An image produced any other way, whether a separate photo session, a phone photo, or an AI-generated image, is built to a different setup, so it sits off-standard next to the others. If someone misses the main session, the clean fix is a short follow-up session to the same setup, so their headshot is a true match rather than an approximation.