GitHub photo as a fully remote worker.

When colleagues only ever see you in a small video tile, the static profile photo carries more identity work than for in-office workers.

Remote workers are referenced visually almost entirely through profile photos. Slack, Notion, GitHub, internal directory, and the corner of every video call all surface the avatar at small sizes. A photo that does not read at thumbnail size makes you forgettable. A photo that does makes you memorable.

15 sec
Generation time
1
Selfie required
8K
Output resolution
$29
20 portraits

Fully remote worker on GitHub.

In-office workers are remembered through hallway interactions. Remote workers are remembered through profile photos and video presence. The static photo has to do more work, which means the cost of a bad photo is higher and the return on a good photo is greater.

Platform-specific guidance.

Remote engineers live on GitHub. A real photo here connects pull request comments to a person colleagues can recognise.

What to fix before publishing the photo.

  1. 1

    High contrast face. Slack avatars and Zoom corners are tiny.

  2. 2

    Same photo across every internal tool. Recognition compounds across surfaces.

  3. 3

    Updated photo when you change cameras, lighting, or wardrobe in your home setup. Match the static and the live versions of you.

  4. 4

    Background simple. Texture and scenery do not read at avatar size.

  5. 5

    Eye contact direct. Colleagues need to feel seen across distance.

  6. 6

    Refresh every 12 months. Remote workers are easier to forget than in-office colleagues, and a fresh photo refreshes recognition.

The GitHub photo standard.

Attire: Whatever you wear to write code. Plain shirt or hoodie. The photo should not overdress the medium. Lighting: Soft, even, neutral. The GitHub avatar appears next to commits and pull request comments. You want to look approachable to maintainers, not posed. Expression: Relaxed neutral or small smile. Open eyes, no pose. GitHub culture rewards photos that look like you on a regular Wednesday at your desk. Framing: Round-cropped. Tight. GitHub serves the avatar small in commit lists and large only on profile pages, so face-first composition wins. Background: Solid colour or a clean backdrop. Save the cool office shot for LinkedIn. Tone: Honest. GitHub culture is allergic to anything that looks like marketing.

Rate your current photo against this standard

Why does the profile photo matter more for remote workers?

Remote workers are referenced visually through static avatars in a way in-office workers are not. Slack, GitHub, Notion, and every internal directory shows your avatar dozens of times per day to colleagues. The photo is doing recognition work that hallway interactions would normally do.

Does the photo need to match how I look on video calls?

Yes. The static photo and the live video presence should match. If your home setup is bright and you wear a blazer on calls, the static photo should reflect that. If your home setup is dim and you wear a hoodie, the static photo should reflect that. Mismatch creates dissonance.

Should remote workers use a photo with a virtual background?

No. The static profile photo is not a video call. Use a real, simple background. Save virtual backgrounds for live calls only.

How often should remote workers refresh the photo?

Every 12 months at most. Remote colleagues are easier to forget than in-office ones, and a refresh reinforces recognition. ThePortraitOS makes the refresh take 15 seconds, removing the usual barrier to updating.

One selfie. 20 portraits. 15 seconds.

Rate your current photo for free, then generate a polished version. 20 portraits for $29, one-time. Credits never expire.

Rate your photo free Generate a portrait