What a Photography Style Guide Actually Is
A style guide for photography is just a living document that keeps your output consistent across shoots, clients, and time. It covers the technical and creative decisions you make before, during, and after a shoot. The checklist version breaks those decisions into discrete, verifiable items so nothing gets skipped or left to memory. I've built these for commercial clients, editorial teams, and my own headshot business. The ones that survive past three months are the ones that are actually usable, not the ones that look impressive on paper.
Core Sections of a Style Guide For Photography Checklist
Here's how I structure mine. It's not exhaustive, but it covers the stuff that actually matters in practice. Pre-Production: - Mood board reference links or images pinned to each shoot brief
- Color palette swatches (hex or Pantone if the client has brand guidelines) - Location or studio reference shots from previous sessions - Shot list mapped to timeline estimates
Get the Full Details
- Wardrobe and props notes tied to the color palette Shooting Parameters: - Camera body and lens kit designated for the project type
- Target exposure settings (ISO ceiling, aperture range, shutter speed floor) - White balance preset or custom profile reference - Lighting ratio targets for key/fill combinations
- Format: RAW only, or RAW + JPEG for client delivery Post-Processing Standards: - Preset or LUT file version (and where it's stored)
- Skin tone correction boundaries (what I consider "acceptable" vs. "overdone") - Background treatment rules (clipped to pure black, lifted to 18% gray, etc.) - Noise reduction and sharpening thresholds per output format
- File naming convention and folder structure Delivery & Archival: - Resolution and file size limits for web vs. print
- Color space designation (sRGB for digital, Adobe RGB or ProPhoto for print) - Retouching tier definitions (basic color correction vs. full beauty retouch) - Backup protocol: where the master lives, where the delivery copy lives
How to Actually Build One Without It Becoming Junk
The biggest mistake people make is writing the guide before they have enough repeated work to know what the patterns actually are. If you've only done three wedding shoots, you don't have a style yet. You have a preference. Preferences change. Styles stabilize after about twenty similar jobs. My process is backwards from what most tutorials suggest. I start with an existing shoot that went well, export the files, and work backwards from the final result to document every decision that got me there. I look at the Lightroom develop settings, note the lighting diagram, write down what I did differently than the previous shoot, and capture the things that almost went wrong. This takes longer upfront but the resulting checklist is accurate instead of aspirational. Aspirational checklists are the ones I find myself ignoring six months later.
One practical habit I picked up: keep the checklist in the same tool chain as your workflow. If you use Capture One, the style guide lives in a folder next to your session files. If you use Lightroom, it's a text file in your preset directory. Friction kills compliance more than anything else.
A Real Problem I Ran Into With This Approach
Last year I was doing a series of product shots for a skincare brand that had very specific color requirements. Their brand guide specified a cool-neutral white balance, but their marketing team kept approving proofs that looked too warm. The discrepancy was subtle — maybe 200–300 Kelvin off — and it only showed up when the images were placed side by side with their other assets. What I ended up doing was adding a color checker target to every shoot, processing a test patch in the same lighting conditions, and locking the white balance to the measured value instead of eyeballing it. I put that step into the pre-production section of the checklist. It added about four minutes to setup but eliminated the back-and-forth revisions entirely. The client stopped sending notes about color consistency after that.
Counter-Intuitive Things I've Learned
Most people think a style guide is about restricting creativity. It's actually the opposite. When your technical decisions are automated by checklist, you have more mental bandwidth for the creative decisions that actually matter in the moment — compositional choices, directing the subject, adjusting to unexpected light. The checklist handles the routine so you don't have to think about it. Another thing: the most useful style guides are the ones that explicitly state what you don't do. "No clipping on skin highlights above 245" is more actionable than "natural skin tones." Specific boundaries prevent scope creep from clients who don't know what they're asking for until they see it.
Where This Falls Apart
A style guide doesn't work when you're doing genuinely one-off work with no precedent. Creative direction photography, experimental fine art, or projects where the client has no fixed vision — those situations resist standardization. Forcing a checklist into those workflows usually makes things slower because you're spending time filling out boxes that don't apply. Also, style guides degrade. Your eye changes, your equipment changes, client expectations shift. A guide written in 2022 that you haven't touched since is probably inaccurate now. I revisit mine quarterly and prune the items that have become second nature. If something appears on the checklist every single time without thought, it doesn't belong there anymore. It belongs in muscle memory. There's also the problem of team handoffs. If you're working with assistants or retouchers, the guide needs to be interpretable by someone who hasn't spent years developing your particular workflow. Overly internal shorthand becomes useless the moment another person touches the files. I've learned to write instructions as if someone competent but unfamiliar is reading them at 9 PM on a Tuesday.
