GitHub Profile Picture Size: 460 vs 500 vs 920 (And Why Your Avatar Looks Blurry)
GitHub gives you three different numbers for the same avatar, and they are not interchangeable: 460×460 is the largest size GitHub renders on your profile. 500×500 is the smallest upload GitHub actually recommends.
GitHub gives you three different numbers for the same avatar, and they are not interchangeable:
- 460×460 is the largest size GitHub renders on your profile.
- 500×500 is the smallest upload GitHub actually recommends.
- 920×920 is roughly what you need for a sharp avatar on a 2× retina screen.
Upload a 460×460 file because it matches the display size, and you have already started one step behind. Upload a 500×500 file and it will look fine on a cheap monitor, then soft on a MacBook. The fix is not a mystery setting inside GitHub. It is choosing the right source resolution before you upload.
The three numbers, explained
| Number | What it means | Where it comes from |
|---|---|---|
| 460×460 | Maximum rendered avatar size on the profile page | GitHub's profile layout |
| 500×500 | Recommended minimum upload size | GitHub's own guidance |
| 920×920 | 2× the largest rendered size | Device pixel ratio math |
| 1 MB | Maximum file size | GitHub upload limit |
GitHub stores one source image and generates every smaller version from it: 20 px next to a commit, 40 px in a comment thread, 460 px on your profile. If the source is smaller than the largest rendered size, GitHub has to invent pixels when it scales up. That is the blur.
Why 500×500 is still not enough on a retina screen
CSS pixels and physical pixels are not the same thing. A profile avatar that occupies 460 CSS pixels is drawn with 920 physical pixels on a 2× display, and 1,380 on a 3× phone. If your upload is 500×500, the browser still has to stretch it to fill those physical pixels.
This is the same reason a 1080p photo looks soft on a 4K monitor. The file has less detail than the space it occupies.
A 920×920 or 960×960 source covers the common 2× case without drama. A 1,380×1,380 source covers 3× phones, but the file gets heavier and GitHub will downscale it anyway. For most people, 960×960 is the sweet spot: enough detail for retina laptops, still easy to keep under 1 MB.
The circle crop changes the composition, not the dimensions
Every GitHub avatar is displayed inside a circle: profile header, commit list, pull request comments, notifications. The upload is still a square; GitHub applies the circular mask.
That means the corners of your square never appear. If a logo, face, or line of text sits near an edge, it gets clipped. Keep the important part inside the central area and preview the image through a circular mask before uploading. A square with a face dead center usually survives. A wide logo lockup usually does not.
This is also why "make it 460×460" is incomplete advice: the dimensions can be perfect and the composition can still be wrong.
Format and file size: what to use
GitHub accepts PNG, JPG, and GIF. The practical rules:
- PNG for logos, icons, screenshots, and flat-color artwork. Sharp edges stay sharp, and transparency is supported.
- JPG for photographs and portraits. Export around 85% quality; the difference from 100% is invisible at avatar size, and the file is much smaller.
- GIF if you want an animated avatar. It works, but every frame gets the same circular crop, and the 1 MB limit is easy to blow past.
Keep the final file under 1 MB. If a PNG export is unexpectedly huge, it is usually a noisy photo saved in the wrong format. Switch to JPG.
A five-minute fix, without uploading your photo to a random server
Most "resize image" sites ask you to upload the file first. For a profile picture that is not ideal, even if the photo is already public.
A browser-side resize does the work locally with the Canvas API: the file never leaves the device. The workflow is:
- Drop the source image into the resizer.
- Crop to 1:1. GitHub always displays a square, so decide the composition now.
- Set the output to 960×960 for retina, or 500×500 if you only need the minimum.
- Export PNG for graphics, JPG for photos.
- Check the file size is under 1 MB.
- Upload it in GitHub under Settings → Public profile → Edit → Upload new picture.
There is a ready-made preset with the 1:1 crop and GitHub dimensions here: GitHub profile picture resizer. It runs entirely in the browser, with no account and no upload.
Don't confuse the avatar with the social preview
Your profile picture is the square avatar on your account. The social preview is a different asset: the wide image shown when someone shares one of your repositories on X, LinkedIn, Slack, or Discord.
GitHub's social preview is 1280×640 (2:1). It lives under the repository's Settings → Social preview, not under your personal profile. If you are cleaning up your GitHub presence, both are worth fixing, but they are not the same file and they do not use the same dimensions.
There is a separate preset for that one: GitHub social preview.
TL;DR
- GitHub renders avatars at up to 460×460.
- Upload at least 500×500, but 920–960×960 is what keeps it sharp on retina screens.
- Keep the subject inside the circular safe area; corners are always cropped.
- PNG for graphics, JPG for photos, under 1 MB.
- Profile picture and social preview are different assets: 1:1 vs 1280×640.
The number that matters is not the one GitHub displays. It is the one you upload.
Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.