Product Photography Style Guide for Studios | Lenso

A product photography style guide records the reusable visual rules for a client account.

It explains how product images should look across more than one job.

The job brief can reference the guide and record the current exceptions.

The shot list can apply the guide to each required output.

The quality-control review can check the final files against it.

A style guide is not a guarantee that every future product will need the same treatment. It is the current baseline the studio and client can review.

Style guide, brief, shot list, and brand guide

Keep the records separate.

Brand guide

A broader brand document can cover:

• Logo
• Typography
• Brand colors
• Voice
• Campaign direction
• General photography mood

Product photography style guide

A narrower operational document can cover:

• Background
• Lighting
• Composition
• Crop
• Shadow
• Reflection
• Props
• Product truth
• Retouching boundaries
• Approved visual references

Job brief

Records the current job goal, products, timing, output groups, review process, decision makers, and exceptions.

Shot list

Records each independently required product output.

A product photography style guide can refer to the brand guide.

It should not repeat the whole brand system.

Decide the scope of the guide

Name:

• Client or account
• Product categories covered
• Channels or placements covered
• Guide version
• Effective date
• Owner
• Client decision maker
• Known exclusions

A guide for tabletop home goods might not control apparel-on-model work.

A guide for product-page stills might not control a seasonal campaign.

State the boundary.

1. Background and environment

Record:

• Background type
• Approved color or surface
• Sweep or horizon treatment
• Transparency rule
• Environmental treatment
• Allowed variation
• Prohibited backgrounds

Use the current client or channel requirement.

Do not make white a universal default.

When a channel requires a specific white value, name the channel, source, region, and review date.

2. Lighting

Record observable choices.

Examples:

• Primary light direction follows Reference A.
• Highlights remain controlled on reflective packaging.
• The label stays readable without flattening the bottle shape.
• The collection uses the same approved contrast range.

Avoid adjectives without a reference.

• Premium
• Clean
• Bright
• Dramatic
• Natural

can mean different things to different people.

State what the word means for this account.

3. Composition, crop, and product fill

Record:

• Default product orientation
• Camera-height or angle reference
• Allowed crop
• Required clear space
• Product position
• Alignment
• Scale relationship across variants
• Known channel exceptions

Do not publish one universal fill percentage.

Use an approved reference or current destination rule.

When an output needs another crop, record the exception in the job and shot row.

4. Shadow and reflection

Record:

• Shadow direction
• Shadow softness
• Shadow density
• Reflection treatment
• Grounding rule
• Allowed natural variation
• Prohibited artificial treatment

Use approved visual references rather than relying only on a number.

The goal is a shared interpretation, not a mathematically universal image.

5. Styling, props, models, and included items

Record:

• Allowed props
• Prohibited props
• Product dominance
• Model or hand use
• Included accessories
• Scale references
• Surface treatment
• Seasonal exceptions

Do not use a prop that implies an accessory or quantity is included when it is not.

State whether a product is shown:

• alone;
• in a bundle;
• in use;
• with scale context.

6. Product truth

Record what must remain accurate.

Examples:

• Product geometry
• Variant color
• Visible quantity
• Included accessories
• Label text
• Package claims
• Material texture
• Finish
• Required marks

The guide should not authorize silent changes to the product.

A job-specific approved exception belongs in the current brief and decision record.

7. Retouching boundaries

Record:

• Temporary dust and fingerprint cleanup
• Permanent texture
• Wrinkle treatment
• Label alignment
• Color reference
• Geometry changes
• Composite elements
• Shadow construction
• Surface cleanup
• Prohibited edits

Use a clear boundary between:

• cleanup;
• current approved treatment;
• change that requires another client decision.

Do not use:

• Make it perfect
• High end
• Polished

as the entire retouching rule.

8. Approved references

Use a small current reference set.

For each reference, record:

• Reference name
• What it demonstrates
• What it does not demonstrate
• Approval date
• Version

Example:

• Reference A demonstrates front-view crop and product position.
• It does not define the seasonal surface.

Remove or archive a reference when it is no longer current.

Do not leave several contradictory images labeled as approved.

9. Channel and placement exceptions

Keep one account-level baseline when practical.

Record exceptions for:

• Marketplace main image
• Client-owned product page
• Collection image
• Paid social
• Email
• Print
• Retailer feed

The current official or client requirement controls each exception.

Do not copy time-sensitive channel numbers into the guide without a source and review date.

10. Naming and delivery context

A reusable naming pattern can belong in the style guide when the client uses it across jobs.

Record:

• Product identifier
• View vocabulary
• Variant vocabulary
• Sequence
• Locale
• Channel suffix
• Final-file extension

The current shot row still records the exact final filename.

The source file and review proof can use other names.

11. Ownership and version changes

Name:

• Studio guide owner
• Client decision maker
• Current version
• Effective date
• Last review date
• Change summary
• Superseded version

Use a new version when a material rule changes.

Examples:

• New package shape
• New label
• New visual direction
• New channel
• New product category
• Changed retouching boundary
• Changed approved reference

Do not quietly replace the guide and keep an earlier client decision attached to it.

Copyable one-page style-guide outline

• ACCOUNT
• Client or account:
• Product categories covered:
• Channels or placements covered:
• Guide version:
• Effective date:
• Studio owner:
• Client decision maker:
• Known exclusions:
• BACKGROUND
• Background type:
• Approved color or surface:
• Transparency:
• Environment:
• Allowed variation:
• Prohibited backgrounds:
• LIGHTING
• Primary direction:
• Contrast:
• Highlight treatment:
• Reflective-product rule:
• Approved reference:
• COMPOSITION
• Default orientation:
• Crop:
• Clear space:
• Product position:
• Alignment:
• Variant consistency:
• Approved reference:
• SHADOW AND REFLECTION
• Direction:
• Softness:
• Density:
• Reflection:
• Grounding:
• Prohibited treatment:
• STYLING
• Allowed props:
• Prohibited props:
• Model or hand use:
• Included accessories:
• Scale reference:
• Seasonal exception:
• PRODUCT TRUTH
• Geometry:
• Variant color:
• Quantity:
• Labels and package claims:
• Material texture:
• Included items:
• Prohibited edits:
• RETOUCHING
• Approved cleanup:
• Color reference:
• Texture:
• Geometry:
• Composite work:
• Shadow construction:
• Prohibited treatment:
• REFERENCES
• Reference A:
• Demonstrates:
• Does not demonstrate:
• Reference B:
• Demonstrates:
• Does not demonstrate:
• CHANNEL EXCEPTIONS
• Destination:
• Current source:
• Reviewed date:
• Exception:
• NAMING
• Product identifier:
• View vocabulary:
• Variant vocabulary:
• Sequence:
• Channel or locale:
• Extension:
• VERSION
• Change summary:
• Approved by:
• Approval date:
• Supersedes:

Use the guide in the current job

In the brief, record:

Use Account Style Guide version 3.

Then add the job-specific exception.

In the shot list, record the row-specific application.

In quality control, check the released file against:

• guide;
• brief;
• shot row;
• current channel requirement;
• approved exception.

Do not expect one guide to answer every product-specific question.

Where to keep the guide

Use the studio's current approved document or asset system.

Reference the guide from the current Lenso brief when useful.

Lenso can keep the job brief, product rows, references, proof decisions, and final files connected.

Lenso is not currently positioned as a dedicated account-level style-guide library or a general digital asset management system.

Do not promise permanent client access to the guide.

Review the guide when the account changes

Review when:

A capacity crunch is another moment the guide has to travel intact, not just an account change — a partner studio picking up overflow work needs to see the actual document before its first frame, the same as any new hire would.

• Packaging changes
• A new product category appears
• The client changes the visual direction
• A new destination creates a real exception
• A recurring review question reveals an unclear rule
• The approved reference changes
• The studio's production method changes the visible result

Do not update the guide merely to refresh a date.

Record a substantive change.

Questions about style guides

Is a style guide the same as a brief?

No. The guide contains reusable account-level visual rules. The brief contains current job-level decisions and exceptions.

Is a style guide the same as a shot list?

No. The guide defines the visual baseline. The shot list identifies the required product outputs.

Who writes the guide?

The studio can draft the operational rules from approved client direction. The authorized client reviewer confirms the current version.

Should every client have a style guide?

Not necessarily. Create one when reusable visual rules need to survive across several jobs, products, or team members.

Can a style guide contain channel requirements?

It can reference current channel exceptions. Use the current official source and review date. Do not treat a time-sensitive rule as permanent.