Resume photo size, placement and file format
400–800 pixels, under 200 KB, top of the page beside your name. Why those numbers, and the header defect our own extraction tests caught: a squeezed name block that silently dropped a phone number.
Last reviewed
Short answer: square or 4:5 portrait, about 400–800 pixels on the long edge, under 200 KB, top of the page, roughly 25–35 mm wide when printed. Head and shoulders, plain background, recent.
The rest of this is why those numbers, and the one failure mode that has nothing to do with the photo and everything to do with where you put it.
Pixel dimensions
A resume photo prints at roughly 25–35 mm wide. At 300 DPI — print quality, and more than any screen needs — that is about 300–420 pixels. So 400–800 pixels on the long edge is already generous, and past about 1000 you are storing detail that no reader and no printer will ever resolve.
Going the other way hurts visibly. Under about 300 pixels a portrait starts to look soft on a laptop screen and obviously degraded when printed, and a blurry photo reads as carelessness in a way that no photo at all does not.
The other pixel question: the page itself
People searching for a resume’s size in pixels are often asking about the sheet rather than the portrait, so both answers are here. A resume is a printed page, and a printed page has a physical size that only becomes a pixel count once you pick a resolution:
| Paper | Physical | At 96 DPI (screen) | At 300 DPI (print) |
|---|---|---|---|
| US Letter | 8.5 × 11 in | 816 × 1056 px | 2550 × 3300 px |
| A4 | 210 × 297 mm | 794 × 1123 px | 2480 × 3508 px |
816 × 1056 is the viewport this site’s own renderer lays a resume out in before printing it, so those are working numbers rather than a conversion done for the article.
The practical point: do not design a resume in pixels. A document built to a fixed pixel canvas — which is what happens in an image editor, or in a design tool set to a screen preset — either exports as a picture with no extractable text, or prints at the wrong scale with the margins clipped. Build it as a document at Letter or A4 and let the pixel count fall out of whatever resolution it is eventually rendered at. Which paper depends on where you are applying: Letter in the US and Canada, A4 essentially everywhere else.
Aspect ratio and crop
- Square (1:1) or portrait (4:5, 3:4). These are what resume layouts are built to hold. A landscape crop of a head is almost always a group photo someone cut down.
- Head and shoulders. Top of the head near the top of the frame, crop somewhere around the chest. A full-length photo shrinks your face to nothing at 30 mm.
- Eyes on the upper third. The single crop rule that makes an amateur photo look composed.
- Not a passport photo. Passport rules exist for machine face-matching, not for looking approachable. A neutral expression is fine; the rigid full-frontal passport crop is not required and reads as institutional.
File size and format
Aim for under 200 KB. This is not aesthetics, it is the upload gate: plenty of application portals cap the whole document at 2 MB and some at 1 MB, and a straight-off-the-phone 6 MB JPEG produces a resume that the portal refuses without telling you why.
- JPEG or WebP for the photo itself. Both compress photographic detail well. PNG does not — it is built for flat colour and line art, and a PNG portrait is often five times the size of the same JPEG at the same visible quality.
- Resize before you insert, not after. Dropping a 4000-pixel image into a document and dragging the corner makes it look small. The full file is still embedded.
- The resume ships as a PDF regardless. The photo format matters only up to the point the PDF is produced.
Where on the page
Top, aligned with your name, on either side. That is nearly the whole rule. A photo is an identifier and it belongs where identifying information already is.
Two placements to avoid. Centred above the name pushes your name down the page and makes the picture the headline. Anywhere below the first section means a reader scanning the second page meets your face after your employment history, which is simply strange.
What a photo actually does to parsing
An image inside a PDF is an image. A parser skips it and extracts the text around it in the order the file paints it, so the picture itself costs nothing.
The cost is the layout it drags in. Placing a photo beside a name normally means turning the header into a two-item row, and a layout change is a change to how text is positioned and painted — which is exactly the class of thing that breaks extraction.
We test this rather than assert it. Our extraction suite runs every template twice, once plain and once with a portrait in the header, and the photo pass immediately caught a defect the plain pass could not see: one template sized its name block to fit its content, so adding a photo beside it squeezed that block and pushed the last contact link off the page. The document looked perfect. A phone number was gone.
That is the real risk, and it is the one people do not check for:
- Contact details inside a header text box. In several design tools the photo header is a box, and a box is the single most reliable way to lose an email address in extraction.
- A squeezed name row. Fine at one name length, broken at another. Nothing warns you.
- A photo in a side column with your contact details. The column extracts after the main flow, so your name and email come out somewhere after your job history.
The mechanism behind all three is in what an ATS reads from your PDF, and the column-order question specifically in are two-column resumes ATS-safe.
How to check yours in thirty seconds
Open your PDF, select all, copy, paste into a plain text editor. If your name, email and phone number are the first things in the pasted text, the photo cost you nothing. If they are missing, or if they turn up after your first job, the header is the problem — not the picture.
If nothing pastes at all, the whole document is an image, which is a total failure and more common than people expect: it happens with scans, phone photographs of a printout, and design-tool exports set to rasterize.
The photo itself
- Plain, uncluttered background. A wall is fine.
- Window light, facing you, no direct sun. Overhead office lighting is the worst common option.
- What you would wear to the interview, one notch above the daily norm.
- Recent. A photo from six years ago is a small credibility problem for no gain.
- No filters, no sunglasses, no selfie angle, no cropped-out second person. A visible arm at the frame edge is noticed every time.
Whether to include one at all
Entirely country-dependent, and the answer flips completely between markets: which countries expect a photo on your CV, and the general case in should you put a photo on your resume. Get that decision right first; sizing a photo you should not be sending is wasted effort.
Where this site fits
GetFinalCV re-encodes an uploaded portrait to a fixed size and format rather than embedding whatever you gave it, so the 6 MB-phone-photo problem cannot happen here — the output is the same weight whether you upload 200 KB or 12 MB.
Every template supports a photo and none require one, and the templates built around a portrait are marked in the gallery. The extraction tests described above run against all of them, with a photo, on every change — which is the only reason we are able to describe that failure specifically instead of warning about it vaguely.