Photo by Leeloo The First from Pexels

TL;DR:
  • A stock licence policy is a written set of rules that defines how your team sources, uses, and manages stock media legally across projects.
  • Enterprise policies must cover platform eligibility, approval workflows, licence types, compliance tracking, and audit procedures.
  • The most critical step: centralize licence proof and assign clear ownership so no one loses track of what was licensed when.
Most enterprises buy stock images from multiple platforms, Shutterstock, Adobe Stock, Freepik, Envato, iStock, Canva. Each team member has access. Nobody's quite sure who licensed what, or if that freelancer's deliverables actually came with proof. Then the legal team asks for an audit, or a client disputes an image, and everything goes sideways.

The fix is a stock licence policy, a living document that tells your team exactly how to source, purchase, and track stock media so you're always audit-ready. Without it, you're gambling with compliance.

Why this matters now

0%
Of enterprises face copyright claims

Stock image licensing isn't a nice-to-have anymore. Regulatory pressure, client demands, and the sheer volume of content most teams produce mean one wrong move can cost thousands in legal fees or takedown notices. A clear policy is how you protect yourself.

Here's what happens without one: a designer uses an image she thought was under the team's subscription. It wasn't. A freelancer delivers work with unlicensed assets embedded. A client's lawyer requests proof of every image in a campaign, and you spend days hunting invoices across dashboards. Each incident erodes client trust and burns operational time.

A well-built policy prevents all of that. It's also table stakes for agencies pitching to risk-conscious enterprises and for any team running content at scale.

Common mistakes and misconceptions

Mistake 1: Assuming one subscription covers everything. Most teams think "we have an Adobe Stock seat" means everyone can use every image. Wrong. Licence limits vary by seat, subscription level, and region. Some images come with extended-use restrictions. One policy error and you're liable, not Adobe.

Mistake 2: Not tracking who licensed what. If you can't prove an image was licensed on your account when a client questions it, you lose. Central tracking isn't optional, it's the backbone of defence.

Mistake 3: Treating freelancers like they know your rules. Onboarding a freelancer without a clear licence policy means they'll buy from their own accounts, use free-tier images they don't have rights for, or embed assets without documentation. Then you inherit the risk.

Mistake 4: Skipping the checklist step. Teams that don't require approval before an image goes live end up with unlicensed or over-used images in production. A simple gate prevents 90% of problems.

Mistake 5: Forgetting to audit. A policy that nobody checks is useless. Audits catch drift and tell you which platforms are being used (and abused).

Step-by-step approach

office desk
Photo by Kampus Production from Pexels

Step 1: Define which platforms are approved

Not every platform is equal. Start by listing the stock sources your team actually uses or should use:

  • Adobe Stock, industry standard, straightforward licensing, integrates into Creative Suite
  • Shutterstock, broad library, good for volume buying
  • Freepik, popular for design teams, confusing free-tier licensing
  • Envato Elements, subscription model, unlimited downloads
  • iStock, premium images, clear commercial licence
  • Canva, built-in licence clarity, good for non-designers
  • Depositphotos, solid general library
Next, block or restrict non-approved platforms. If a designer uses DaFont or finds images on Google Images, those are unlicensed landmines. Your policy should say: "Only images from approved platforms are permitted in client work."

Also set account-level limits. For example: "Only the Adobe Stock admin account may purchase seats; team members may not create personal subscriptions." This keeps licensing centralized and auditable.

Step 2: Create an approval workflow

team meeting
Photo by RDNE Stock project from Pexels

Every image used in client-facing work must pass a gate. Here's a simple three-step flow:

  1. Designer selects and documents the image. Screenshot the licence terms (or download the licence certificate). Note the platform, image ID, and intended use.
  2. Project lead reviews for compliance. Check: Is it from an approved platform? Does the licence cover the intended use (editorial, commercial, print, digital)? Is there any geographic restriction?
  3. Approve or reject. If approved, move forward. If rejected, designer finds an alternative.
This sounds like bureaucracy, but it takes 30 seconds per image and catches the vast majority of problems before they reach production.

Step 3: Document licence terms clearly

Your policy must spell out what each licence type actually means. Misunderstanding licence scope is the biggest source of disputes.

  • Standard commercial licence: Use in client work, digital and print, for the end client's business purposes. Redistribution and resale typically not allowed.
  • Extended licence: Broader usage rights; sometimes includes templates, derivatives, or limited resale. Usually costs 2-5x the standard licence price.
  • Editorial licence: Images can only be used with reporting, journalism, or news context. Cannot be used to endorse or sell a product.
  • Rights-managed (RM): Limited to specific uses (e.g., "US market only, 6-month duration, 100,000 impressions"). Requires negotiation.
  • Royalty-free (RF): No ongoing royalties, but still restricted by licence agreement. "Royalty-free" does NOT mean "free to use however you want."
Include a one-pager in your policy document showing what each type covers and doesn't cover. Circulate it to designers and make sure they ask questions.
"ChiliPiper increased their close rate by 28% after implementing PandaDoc."
>, How to Create a Comprehensive Enterprise License Agreement

Step 4: Set up centralized tracking and proof storage

Every licensed image must have a record. Create a simple spreadsheet or database that includes:

  • Image ID (e.g., Adobe Stock #12345678)
  • Platform (Adobe Stock, Shutterstock, etc.)
  • Licence date
  • Licence type (standard, extended, editorial)
  • Licensed for (project name, client name)
  • Who licensed it (which team member or account)
  • Expiry date (if applicable)
  • Certificate link or file path
Store the actual licence certificate or proof of purchase alongside it. Most platforms allow you to download a PDF certificate showing the image, licence type, and terms. File it in a central location, Google Drive, Dropbox, or a dedicated asset management tool.

Why does this matter? If a client or their legal team ever asks "where did this image come from," you can pull the proof in seconds. Without it, your word alone isn't enough.

Step 5: Create an onboarding and offboarding checklist

When someone joins the team, walk them through your policy. Show them where to find approved platforms, how to request a licence, and where to document it. Send them the licence-type one-pager. Have them sign off that they understand the rules.

When someone leaves, audit their projects. Did they use any personal subscriptions? Did they download any licence certificates to their own accounts? Did they hand off access to any paid platforms? If you don't do this, you inherit orphaned assets and potentially unlicensed material.

Step 6: Schedule regular audits

planning session
Photo by Ketut Subiyanto from Pexels

Quarterly, pull a random sample of recent projects. Cross-reference every image to your tracking spreadsheet. Ask:

  • Does it have a licence certificate?
  • Is the licence active (not expired)?
  • Does it match the intended use?
  • Is the asset stored correctly?
If something is missing or wrong, flag it and loop in the responsible team member. Use findings to refine your policy.

Also audit your accounts themselves. Which platforms is your team actively using? Are there redundant subscriptions? Are seats going unused? This keeps costs down and reduces complexity.

Tools and workflows that help

Teams using centralized asset management report higher compliance
0%

Asset management platforms like Frame.io, Canto, or Bynder let you store images with metadata, including licence info. They integrate with Creative Suite and streamline approvals.

Spreadsheet templates are free and often sufficient. Google Sheets or Airtable can track every image and link to certificate files. For teams under 50 people, this works fine.

Automated reminders help enforce the policy. Tools like Zapier or Slack integrations can notify team members when a licence is about to expire or when they haven't documented an asset in 48 hours.

Platform-specific features matter too. Adobe Stock lets admins set usage limits and see reports. Shutterstock has team dashboards. Freepik allows bulk downloads with batch-generated certificates. Know what your platforms offer and use it.

One more critical tool: Licence Downloader. If you manage subscriptions across multiple platforms, manually tracking and downloading certificates for hundreds of assets is soul-crushing. Licence Downloader automates bulk certificate retrieval from Freepik, Shutterstock, Adobe Stock, Envato, and others, so you can download proof for your entire library in minutes instead of days. It's built for teams exactly like yours.

Interactive policy workflow

To visualize how all these steps fit together, here's a walkthrough of a typical enterprise licensing day:

Daily Enterprise Licensing Flow

1
Designer finds image on approved platform (e.g., Adobe Stock)
2
Documents the licence, captures image ID, platform, licence type, intended use
3
Downloads certificate from platform and stores in central location
4
Submits to project lead for compliance check (15 seconds)
5
Lead approves or flags, if flag, designer finds alternative
6
Image enters tracking database and goes into client work
7
Quarterly audit verifies all images are documented and active

This workflow turns a chaotic, high-risk process into something repeatable and defensible.

Key takeaway: A stock licence policy is not a legal document you write once and file away, it's a living system that protects your team through clear approvals, central tracking, and regular audits.

Enterprise Stock Licence Policy Checklist

Your progress is saved automatically in your browser.

FAQ

Frequently Asked Questions

Assign one person (ideally a production lead or operations manager) as the licence policy owner. They drive adoption, handle exceptions, run audits, and update the policy as platforms or team needs change. Everyone else follows it. A policy with no owner drifts immediately.
If you're starting from scratch: 2-3 weeks to design the policy, set up tracking infrastructure, and draft templates. Onboarding the team takes another 1-2 weeks. For a team under 50 people, the whole process is a month of part-time work. Agencies managing 100+ ongoing projects should budget 6-8 weeks and may want outside help.
Audit what you're already doing. Spend a day pulling a recent project and asking: What platforms did we use? Where are the certificates? Who licensed what? This tells you the size of the gap and what your biggest risks are right now. Start there.
Not recommended. It creates audit nightmares and orphaned assets. Instead, give freelancers access to your team accounts (read-only on most platforms) or reimburse them for platforms they use on your behalf. Always require them to document and hand over certificates before you accept deliverables.
Pull the licence certificate from your central storage and send it to them. You should be able to do this in under a minute. If you can't, your tracking system needs work.
Check three things: (1) Is it from an approved platform? (2) Do you have a certificate showing it was purchased under your account? (3) Does the licence cover the intended use? If all three are yes, you're good. If any is no or unclear, find a different image.

The hardest part of building a stock licence policy isn't the rules, it's actually following them. Consistency matters more than perfection. Even a simple spreadsheet-based system that actually gets used beats a beautiful policy that nobody remembers. Start small, make it non-negotiable, and refine as you learn what works for your team.

Additional Resources

What's your biggest licence management headache right now?