Fixing a Faculty Directory Where Every Photo Looks Different

What the grid actually breaks on

Before writing rules, look at your own directory and identify what causes the visual chaos, because it is rarely photographic quality. The four repeat offenders are background colour, head size within the frame, brightness and crop shape. A grid of technically mediocre photos that share those four attributes reads as coherent. A grid of beautiful photos that do not share them reads as a jumble.

Head size is the one people miss. If one portrait is framed from the chest up and the next from the waist up, the faces render at noticeably different sizes in equally sized tiles, and the eye reads that as disorder before it reads anything else. Aligning head size across the grid produces a bigger improvement than any other single change.

Orientation and aspect are next. Some directories crop to a square, some to a circle, some to a tall rectangle. A photo composed for one shape and forced into another loses the top of a head or gains a large empty area beside it. Decide the shape the grid uses, then make every image serve that shape.

• Background: colour, tone and busyness
• Head size and eye line position within the frame
• Overall brightness and contrast
• Crop shape and orientation
• Colour versus black and white, which should never be mixed in one grid

The one-page standard

Keep it to a single page, because a three-page photography specification will not be read by a department administrator submitting a photo at 4pm on a deadline day. Specify the background, the framing, the orientation, the minimum resolution, whether colour or monochrome, and rough attire guidance. Say what to avoid as clearly as what to do: no group crops, no sunglasses, no heavy filters, no screenshots.

Write framing in terms anyone can apply without a photographer's vocabulary. Something like: shoulders visible at the bottom edge, a small gap above the head, eyes about a third of the way down the frame, face square to the camera or turned slightly. Add a single example image, which communicates more than a paragraph of description.

On attire, guidance rather than rules works better in an academic setting. Say what the institution is aiming for and leave room, because a hard dress code in a faculty portrait standard generates more argument than it is worth and can run into cultural and religious considerations you do not want to be adjudicating from a marketing office. If your institution has an equality or HR position on appearance, align with it rather than inventing your own.

Reshoot who you can, on a schedule people will actually attend

The cheapest way to build a consistent directory is one repeated setup. Book a room with a plain wall and a large window, or a single portable backdrop and one light, and hold recurring sessions: a full day at the start of each term, plus a standing half hour every fortnight for new starters. The same room and the same setup means every portrait shares background and lighting without anyone having to think about it.

Make attendance frictionless rather than mandatory. Sessions in the building where people already are, no booking required, five minutes each, and photos delivered to the individual within a couple of days. Compliance follows convenience far more reliably than it follows policy emails.

Photograph everyone against the same background even if they insist on their own clothing choices, expression or angle. Personal variation within a consistent frame is fine and even desirable; a directory of identical expressions looks like a corporate brochure. The consistency you need is environmental, not personal.

Retrofitting the photos you cannot reshoot

You will always have a residue: staff on sabbatical, staff at a partner campus, emeritus professors, and the one who simply will not sit for a new photo. For these, the goal is not a perfect match but a close-enough one, and the levers are background, brightness and colour temperature. Bring the background to a similar tone, lift or lower the exposure to match the set, and neutralise any strong colour cast.

This is a good use for Foxi AI. You upload the existing portrait, describe the target look in plain words, and the edit changes the background and lighting while leaving the person's actual appearance intact, which is exactly the boundary a staff directory has to respect. Everyday looks run about 5 credits, so bringing a couple of dozen legacy portraits into line is a modest and predictable cost, and the same balance works across web and mobile if different people in the team are doing the work.

Be honest about the limits. A low-resolution photo cropped out of a group shot will not become a good portrait, and an editing pass cannot invent detail that was never captured. If someone's only available image is a 200-pixel thumbnail from 2009, the right answer is to keep pressing for a new one, or to use a neutral placeholder, rather than to publish something that looks broken next to the rest.

The professor who will not have their photo taken

Every institution has them, and the reasons vary from mild dislike of being photographed to genuine privacy or safety concerns, some of which are entirely legitimate and none of which you should override. Whether a staff photograph can be required at all can touch on employment terms and on data protection expectations, and that varies by country and institution. Take that question to HR and your data protection contact rather than settling it from a style guide.

Have a defined fallback so the grid does not break: a consistent placeholder tile using the institution's mark, styled to sit in the grid rather than shout. That is much better than leaving a broken image icon or a blank grey square, and it removes the pressure to publish someone's twelve-year-old photo against their wishes.

For the merely reluctant, the objection is usually the experience rather than the outcome. Offering a five-minute slot in their own building, showing them the frames, and letting them pick converts most of them. Sending a photographer to their office is often the whole solution.

Crop rules that keep the grid stable over time

Write down the crop as a rule anyone can follow rather than a set of pixel dimensions, because pixel dimensions go stale the next time the site is redesigned. A rule like eyes at one third from the top, head occupying roughly half the frame height, shoulders reaching the bottom edge, will survive a redesign; a rule that says 400 by 400 will not.

Keep master files at higher resolution than the grid needs and export crops from them. When the design team switches from square tiles to circular avatars, you re-export rather than re-crop, which is how faces avoid gradually losing their foreheads across successive redesigns. Store masters by name, exports by placement.

Do not hard-code any platform's stated image requirements from memory, whether that is your CMS, a research profile service or a conference site. Requirements change; check the current documentation each time you prepare a new set. The internal rule stays stable, the exports adapt to it.

Frequently asked