Name Headshots So Your Whole Team Can Find Them Instantly

Start With This Simple Three-Part Formula

Picture this: your marketing director emails at 4:45 PM. "I need James Chen's headshot for the press release in 30 minutes." You panic. You search your drive for "James," "Chen," "JC," "Portrait_12." You find seven files: "IMG_4590.jpg," "Best_One.jpg," "Chen_Crop_Final.jpg." None are right. That scramble ends now.

Use this formula for every single file: Lastname_Firstname_Keyword.jpg. That's it. "Chen_James_Executive.jpg." "Smith_Aisha_Tech.jpg." "Rodriguez_Marcus_Casual.jpg." I've seen teams waste 40 collective hours a month on wild goose chases for images. This three-part tag stops the hunt cold. The name tells you exactly who it is and what version you're getting.

Build Your Naming Structure for Portraze Files

Let's get specific about that third part, the keyword. It's not random. It describes the image's use. Think of it like a uniform code your whole company learns in five minutes.

For standard corporate headshots, I recommend four core keywords: Executive (suit, formal background), Business (blazer, more approachable), Casual (sweater or company polo), and Website (specific crop for your site's template). A fifth, Social, is great for square crops. So you get: "Patel_Sanjay_Executive.jpg" and "Patel_Sanjay_Social.jpg."

One client had a folder with "Sanjay1," "Sanjay_approved," and "Patel_FINAL." After we switched, their HR manager found the needed file in under 10 seconds. That's the power of a structure, not a guess.

The One Folder Rule for Company-Wide Access

Where you put the files matters as much as their names. I enforce a single, sacred folder: "Company_Headshots." No subfolders by department. No subfolders by year. Just one place.

Why? Subfolders create silos. The finance team keeps a "Finance_Headshots" folder, marketing has their own, and soon you have three different versions of the same person floating around. The new intern uses the outdated one from the 2022 folder for the annual report. It looks sloppy.

Put every employee's final, approved headshots in that one master folder, named with our formula. Grant "view only" access to everyone in the company. Now, whether you're in sales in Dallas or engineering in Berlin, you go to the same spot, search "Lastname," and get what you need. Instant access, zero confusion.

Avoid the Chaos of 'Final_Final_v2.jpg'

We've all been there. You're editing and save "Headshot_v1," then "Headshot_v2_Final," then "Headshot_Final_Revised." This habit destroys systems. Those "final" files are drafts. They don't belong in the company master folder.

Here's my rule: the master folder only contains the delivered images. All your editing, your proofs, your drafts live in a separate, private "Working" folder. Only when a shot is approved and ready for the whole company do you export it, name it with the official formula, and drag it into the master "Company_Headshots" folder.

This means the file "Chen_James_Executive.jpg" is the absolute, definitive version. There is no "v2." If you need to update James's headshot next year, you replace that file. One source of truth, forever.

How This Saves 15 Minutes Per Request Forever

Let's do the math. A mid-sized company fields about 20 headshot requests a week—for the website, a conference, a newsletter. If each request triggers a 15-minute search, that's 5 hours of paid time spent hunting.

With the system, the search takes 15 seconds. You open the folder, start typing "Ch..." and "Chen_James_Executive.jpg" appears. You drag it into the email. Done.

That's a saving of roughly 14 minutes and 45 seconds per request. Over a year, that's about 250 hours recovered. That's time for your team to do actual work, not digital archaeology. It eliminates the "I can't find it" email chain, the frantic Slack messages, the last-minute panic.

Start with one person. Rename their files using Lastname_Firstname_Keyword. Put them in a new folder. Show one colleague how to find it. The relief on their face will tell you everything. Consistency is quiet, but the time it gives back is loud.