Your Slack Profile Picture Is the Work Photo People Actually See

Your Slack profile picture is the work photo your colleagues see most. It sits beside every message you send, all day, at roughly the size of a fingernail. A LinkedIn headshot gets looked at a few times a year. The internal avatar gets looked at a few hundred times a week — by the people who assign your projects.

Why Your Internal Avatar Outranks Your LinkedIn Photo

Frequency beats polish. Gallup's Hybrid Work Indicator puts 52% of remote-capable US employees in hybrid arrangements, 26% working exclusively remotely and 22% fully on-site. Gallup's separate analysis of hybrid schedules finds those hybrid employees now spend about 46% of the workweek in the office — the equivalent of roughly 2.3 days. For all of these people, the chat client is the hallway, and the avatar is your face in it.

The asymmetry is stark. A LinkedIn profile photo is viewed in bursts: when you apply for something, when a recruiter sources you, when someone you just met looks you up. A Slack or Teams avatar is viewed continuously by the people who assign your projects, review your work and say your name in calibration meetings. Over a year, the internal photo probably accumulates more impressions from decision-makers than the external one does from everyone combined.

There is also evidence that the avatar does interpretive work, not just decorative work. In Affective Profile Pictures, a controlled online experiment with 186 participants presented at CHI 2023, researchers found that the facial expression in a sender's profile picture shaped how recipients perceived the sender and how they read the emotional tone of neutral messages. Pairing a profile picture whose expression clashed with a positive message dampened how positive that message read. Negative messages were largely unaffected.

That matters because workplace chat is overwhelmingly neutral in tone. "Can you look at this by Thursday." "Reverting the change." "Ping me when you're free." Those messages carry almost no emotional signal of their own, so readers borrow one — from punctuation, from response latency, and from the small round photograph sitting next to the text. If your avatar is a squinting crop from someone else's wedding, that is the tone it lends.

It is worth being concrete about where the thing actually appears:

• Next to every message you post in Slack's default display theme, plus DMs, huddles, mention hovercards and the member directory.
• In Microsoft Teams, it doubles as your Outlook sender photo, your SharePoint contributor photo and your face in Microsoft 365 search results.
• On every meeting tile when your camera is off — which, for most people, is a meaningful share of meetings.
• As the first thing a new hire attaches to your name, often weeks before they hear your voice.

Slack Profile Picture: The Verified Specs

Slack publishes a narrow and unusually specific range. Its help documentation states that a profile picture should be a minimum of 512x512 pixels and no larger than 1024x1024. The API that sets photos programmatically repeats the same limits and mentions JPEG, GIF and PNG. Square goes in; a circle comes out.

• Dimensions: minimum 512×512 pixels, maximum 1024×1024 pixels. Slack's help article and its users.setPhoto API reference state the same range.
• Shape: upload a square. Slack's API letterboxes non-square images when no cropping instructions are supplied, and the upload dialog will hand you a cropper. Either way, the crop is a decision — make it deliberately in your own editor rather than in a hurry in a modal.
• Formats: JPEG, PNG and GIF. For a photograph, a high-quality JPEG is the right call — smaller file, no visible penalty.
• Fallback: with no photo uploaded, Slack shows a default placeholder rather than leaving blank space, so "no photo" is still a choice that renders.

Two Slack-specific behaviors change the calculus. The first is display density. Slack's Messages & media preferences offer a Clean theme and a Compact theme, and Slack states plainly that the Compact theme "uses less white space between messages and hides member profile photos." A meaningful slice of your colleagues — the heavy users, typically — have switched your avatar off entirely.

The second is external exposure. In Slack Connect, the default "basic details" setting shares your name and profile photo with the external organizations in your shared channels; the alternative, "standard work details," shares more rather than less. Your internal avatar is therefore also a client-facing asset at any company running shared channels with customers, vendors or agencies, whether or not anyone mentioned that when you joined.

Microsoft Teams Profile Picture: The Verified Specs

Microsoft is vague in its user-facing help and precise in its developer documentation. The Teams support article on changing your picture gives no dimensions at all. Microsoft Graph does: the largest HD photo size stored on a Microsoft 365 account is 648x648, with a fixed ladder of smaller derived sizes beneath it.

• Largest stored size: 648×648 pixels. Microsoft Graph documents this as the top of the HD photo ladder for Microsoft 365 accounts.
• Derived sizes: 48×48, 64×64, 96×96, 120×120, 240×240, 360×360, 432×432, 504×504 and 648×648. Microsoft's own example is explicit: upload a 504-pixel photo and every size except 648×648 becomes available.
• Exception: photos stored in Microsoft Entra ID rather than Exchange can be any dimension.
• File size: Microsoft's admin documentation puts the maximum supported photo size at 4 MB — a ceiling a 648-pixel JPEG will not come close to.
• Practical recommendation: upload a square JPEG at 648×648. It is the largest size the platform retains, and every smaller rendition is generated from it.

The most important Teams fact is not a number: your Teams photo is not a Teams photo. For work and school accounts it is your Microsoft 365 profile photo, which means changing it in Teams also changes it in Outlook, SharePoint, OneDrive, Microsoft 365 search and profile cards across the suite. There is no chat-only version. Whatever you upload becomes the photo on emails you send to customers.

That coupling explains the most common complaint about Teams photos: you changed it and it did not change. Microsoft 365 caches profile images aggressively across services, and Microsoft's own support article notes that it may take time for the settings to update across your channels, suggesting a cache clear to speed things along. Give it hours, not minutes, before concluding something is broken.

Administrators have a lever here too. The Outlook Web App mailbox policy exposes a SetPhotoEnabled setting; switching it off prevents users from changing their own photo, and Teams honors that policy alongside Outlook and SharePoint. Microsoft has since added photo update settings configurable through Microsoft Graph, and warns that changes there can take up to 24 hours to propagate. Some regulated organizations use these controls to lock a directory image. Most organizations should not, for reasons covered further down.

What Survives at 32 Pixels, and What Turns to Mush

Downscaling is a destructive operation. When a 648-pixel image is drawn into a 32-pixel circle, about 99.8% of the original pixels are discarded, and whatever information depended on fine detail goes with them. What remains is shape, contrast and color mass. Design for those three things and nothing else.

Chat clients render message-list avatars small — on the order of 24 to 48 CSS pixels wide, depending on the client, the density setting and your display scaling. On a standard-density screen that is smaller than a lowercase letter in this paragraph. Nothing about your photograph is legible at that size except the broad arrangement of light and dark.

What holds up

• A tight crop. Head and the top of the shoulders, eyes sitting in the upper third of the frame. Anything looser and your face occupies too few pixels to identify.
• Contrast between subject and background. A dark jacket against a dark wall merges into one blob. The same jacket against a light gray wall keeps a readable silhouette.
• A single uncluttered background. Plain walls, soft gradients and heavily blurred environments all survive the shrink. Bookshelves, foliage and cityscapes become visual static.
• Broad expression. At avatar size you cannot resolve teeth or crow's feet. What reads is mouth shape and overall face geometry, so a clear, generous expression beats a subtle one.
• Even, directional light. Flat frontal light collapses facial structure into a single tone; gentle side light carves shadows that survive downscaling as recognizable shape.

What turns to mush

• Full-body or three-quarter-length shots. Your head ends up about eight pixels across.
• Group photos, including the classic crop from a wedding party. At 32 pixels the second person is an unexplained smudge next to your ear.
• Sunglasses and heavy backlighting. Both remove the eyes, which are the highest-information region at small sizes.
• Text, logos or watermarks. Illegible at avatar size, and they consume the pixels your face needed.
• Busy patterns — plaid shirts, striped backdrops, patterned wallpaper. Downscaling turns fine repeating detail into noise.

Background choice does more work here than almost any other variable, and it is the easiest thing to fix without retaking anything. Our guide to choosing a headshot background covers the general principles by use case; the companion piece on what actually works in a small circular crop is the one to read if your specific problem is that a good photo stops working the moment it is shrunk to a circle.

Should Your Internal Photo Match Your LinkedIn Photo?

For most people the answer is yes, and the reason is mechanical rather than aesthetic. Both platforms leak your internal photo outward. Slack shares your name and profile photo with external organizations in Slack Connect by default, and your Teams photo is your entire Microsoft 365 photo, including the one on outbound email.

So the practical question is not really whether they should match, but how many photos you are maintaining and where each one surfaces. For most people the honest answer is one. A single current photograph, cropped once for a circle, used across Slack, Teams and LinkedIn, is far easier to keep current than three near-duplicates that quietly diverge over four years.

There are a few defensible reasons to run a deliberately different internal photo:

1. 1Register. Some workplaces genuinely are more casual internally than the market-facing brand. A softer frame inside and a sharper one outside is coherent — provided both are unmistakably the same person.
2. 2Recency. If your public photo is three years old and you have since changed your hair or started wearing glasses, the internal one should be the current one. Colleagues need to recognize you on video; recruiters need to recognize whoever walks into the interview.
3. 3Privacy posture. Some people are comfortable being identifiable inside a company and not on a public profile. That is legitimate — though Slack Connect and Microsoft 365 external sharing narrow the gap more than most people assume.

What is not defensible is letting them drift apart by accident, which is the usual state of affairs. If you cannot remember when you last changed either one, our piece on how often to update your profile photo gives a rule that transfers cleanly to the internal directory: replace it when it stops matching what someone would see on a video call.

Photo, Cartoon Avatar or Illustration: What Each One Signals

There is no neutral option here. A directory of real faces, a directory of cartoon avatars and a directory of gray initials each say something different about how a company treats identity, and employees read those signals faster than they read any culture deck.

• A real photograph. Signals a company where people are individually visible. It is the default expectation in most professional contexts and by far the strongest option for recognition. The cost is that it requires everyone to have a usable photo, which is precisely where these programs stall.
• An illustrated or cartoon avatar. Reads as playful, and in some engineering, gaming and open-source cultures it is the norm rather than the exception. It preserves privacy and sidesteps appearance anxiety. The cost is real: illustrations are much harder to map to a face on a call, and a directory of them makes onboarding slower.
• A logo, a pet or an object. Usually reads as either "I did not want to do this" or "I am opting out of visibility." Neither is fatal, but both cost a small amount of presence in a medium where presence is already scarce.
• The generated default. Initials on a colored square. Functionally a nameplate: it identifies you and adds nothing. In a large workspace, a wall of defaults makes everyone marginally harder to tell apart.

The right answer depends on what the team optimizes for. A twelve-person team that meets on video every day can run cartoon avatars with almost no friction, because everyone already knows every face. A four-hundred-person distributed organization where most collaboration is asynchronous and cross-functional cannot — there, the avatar is doing identification work that nothing else in the interface does.

One rule holds across all of them: whatever you pick, keep it stable. People build a visual index of their colleagues over months. Changing your avatar every few weeks quietly resets that index, and you become slightly harder to find in a crowded message list every time you do it.

The Recognition and Accessibility Case for Real Faces

Real faces are not only a warmth play. They are a recognition aid, and for some colleagues they are the primary one. Estimates of how many people have developmental prosopagnosia — a lifelong difficulty recognizing faces — vary widely with the diagnostic threshold used, but the Cleveland Clinic cites research suggesting as much as 2.5% of people have it to some degree. Even at the conservative end of the published range, that is someone on most teams.

Prosopagnosia sits on a spectrum, from mild trouble telling similar-looking people apart to an inability to process faces as meaningful at all. People who have it compensate with other identifiers: voice, mannerisms, hairstyle, clothing, seating position, context. Face Blind UK's workplace guidance leans on exactly these — clear name badges, attendee lists, stable seating, explicit introductions in group discussions.

Notice that remote work removes nearly all of them. There is no seating chart in Slack. There is no voice in a written thread. Clothing changes daily and hairstyle is invisible in a 32-pixel circle. What remains is the name string and the avatar — which is why a stable, consistent, real photograph functions as an accessibility feature for those colleagues rather than a nicety.

The same logic extends to more ordinary cases. New joiners spend their first weeks attaching names to faces at a company they have never physically visited. Colleagues in adjacent time zones may interact with you in writing for months before a live call. People with low vision benefit from high-contrast avatars for the same reason everyone does, only more so — and chat clients give you no alt text field to compensate with.

This is the strongest practical argument for treating the directory photo as infrastructure rather than vanity, and for building it into onboarding instead of leaving it to individual initiative. Our walkthrough on making a photo part of week one covers how to slot it into the first-week checklist without it feeling like an initiation ritual.

A Rollout Playbook for IT and People Teams

The failure mode of a directory photo program is not resistance. It is drift: strong adoption in month one, new joiners who never got the memo, and three visual eras of the company coexisting in a single member list. Consistency is a process problem, not a photography problem.

What to standardize

1. 1A single written spec. Square, 648×648 or larger, JPEG, head-and-shoulders crop, plain background, taken within roughly the last two years. Publish it once and link it from onboarding, the intranet and any refresh reminder.
2. 2A background convention. Not a mandated color, but a stated preference — plain, light, uncluttered — so the member list does not look like fifteen different studios stitched together.
3. 3One canonical upload path. In Microsoft 365, upload once and let it propagate rather than asking people to update four apps. In Slack, keep the source file somewhere shared so nobody is re-cropping from memory in a hurry.
4. 4A refresh trigger. Tie photo updates to something that already happens — an annual review cycle, a role change, a rebrand — rather than a standalone campaign nobody remembers in six months.
5. 5A route for people who cannot easily get one. Remote employees in cities with no company office are the most likely to end up with no photo at all, and they are exactly the people who most need one.

What not to mandate

• Do not lock photos administratively unless you have a genuine compliance reason. SetPhotoEnabled will freeze the directory, and it will also remove people's agency over how they are represented all day. That converts a small culture win into a small grievance.
• Do not require a specific expression, wardrobe or background color. Requirements produce compliance-shaped photos. Preferences produce better ones.
• Do not make a photo a condition of anything. Some people have safety, religious or personal reasons to stay unphotographed, and a policy with no exception is a policy that will generate one the hard way.
• Do not run a one-time drive and declare victory. Adoption decays with headcount growth; without a maintenance step, you will be back where you started within a year.

If you are building this from scratch, two companion pieces do the heavy lifting. Our copy-paste company headshot guidelines template gives you the spec document to adapt, and the guide to team headshots for remote teams tackles the harder problem of getting a consistent look when your people are spread across eleven cities. The first is the policy; the second is the logistics.

The Fifteen-Minute Version

If you only do one thing after reading this, do the crop. Most bad internal avatars are not bad photographs. They are decent photographs cropped for a large rectangle and then squeezed into a small circle. Re-cropping an image you already own costs nothing and fixes most of the problem.

1. 1Open the photo you would use. Crop it square, tight to the head and shoulders, with your eyes in the upper third.
2. 2Zoom the preview out to about 5% and look at the thumbnail. If you cannot tell it is you, the crop is too loose or the background is too busy.
3. 3Export at 1024×1024 for Slack and 648×648 for Microsoft 365. JPEG, quality 90 or higher.
4. 4Upload to both, then check how it looks in the member list and in a hovercard — not just in the settings preview, which shows it far larger than anyone else ever will.
5. 5Use the same file on LinkedIn unless you have a specific reason not to. If wardrobe is the thing holding you back, our guide to what to wear for a headshot is the shortest path to a decision.

None of this requires a photographer, and most of it does not even require a new photograph. It requires deciding that the small round picture next to your name is doing a job — tone, recognition, presence — and then making it do that job well. Most people never make that decision, which is why the bar in a typical member list is low enough to clear with a good crop and a plain wall.