Free Stock Photos: Licenses, Sources, and How to Optimize What You Download

Quick answer

Before using a free stock photo, read the source’s license and check whether people, brands, or property need additional permissions. Keep a record of the source and license. Crop and compress the downloaded file for your layout, and add alt text that describes its role on your page.

Reference for this answer: Google image SEO guidance.

The License Landscape in Plain Terms

Every free photo site attaches one of a few license types to its files. You do not need a law degree. You need to know four terms.

Two more concepts sit outside these labels but matter just as much:

• Commercial use means the image supports a business goal: a landing page, an ad, an app screenshot, a client deliverable. Most free licenses allow this. Editorial-only licenses do not.
• Model release is a signed permission from an identifiable person in the photo. Property release covers identifiable private property, artwork, or branded products. These are contracts between the photographer and the subject. The site license does not grant them. If your use implies that a person endorses your product, no site license protects you.

The Major Free Sources Compared

Each big platform runs its own license. The differences look small until a lawyer asks about them.

Unsplash

The Unsplash License lets you use photos commercially without attribution. You cannot sell unmodified copies or build a stock-download site from their catalog. Photographers upload under this license voluntarily, which is why the catalog skews artistic and lifestyle-heavy.

Pexels

The Pexels License also drops the attribution requirement. Its restriction list is more explicit than Unsplash’s: do not show identifiable people in an offensive or negative context, and do not resell the images unchanged. Pexels and Pixabay share ownership, so catalogs overlap.

Pixabay

Pixabay moved off pure CC0 years ago. Today most files carry the Pixabay Content License. It reads like Pexels’ terms: free for commercial use, no attribution, but no redistribution of unedited files as stock and no unflattering depictions of identifiable people. Illustrations and videos follow the same structure.

The smaller sources

Burst targets ecommerce store owners, so the catalog leans toward retail subjects. Kaboompics specializes in interior and lifestyle shots and asks that you not redistribute originals. Rawpixel scans historical archives alongside modern shoots, which makes it strong for public domain material but weak on consistency: one page can mix three license types.

Openverse and Wikimedia Commons are aggregators and archives rather than polished stock sites. Openverse indexes Creative Commons works across the web, so you always inherit the source license. Commons hosts millions of files with wildly varying terms, including editorial-only press photos. Both reward careful users with material the commercial sites cannot offer.

What Every Free License Forbids

The wording differs, but the forbidden list repeats across platforms:

1. Resale as-is. Downloading a photo and selling it, alone or in a pack, violates every major free license.
2. Competing stock platforms. Rebuilding Unsplash inside your own app breaks the Unsplash License.
3. Identifiable people in bad contexts. A recognizable face next to a scandal headline, a political message, or a mock health claim invites both a license violation and a potential publicity-rights claim from the person.
4. Trademarked objects in endorsements. A photo showing a Nike shoe or a Coke bottle does not let you imply those brands sponsor you. Crop, blur, or pick a cleaner frame.
5. Editorial misuse. Files labeled editorial-only never appear in marketing material.

When a project has real stakes, such as a national campaign or packaging, paid libraries earn their price. Paid licenses come with indemnification: if a claim lands, the library’s legal exposure replaces yours. Free licenses offer no such backstop.

Paid Versus Free: The Honest Tradeoffs

Free catalogs have improved enormously, yet gaps remain.

• Saturation. Popular free photos appear on thousands of sites. Visitors recognize them.
• Depth by niche. Free sites cover lifestyle well. Industrial equipment, regional medicine, or specific professions get thin coverage.
• Consistency. Paid sets come from curated shoots with matched color and lighting. Free picks across five sources rarely match.
• Releases. Paid agencies track model and property releases. Free sites usually do not tell you whether a release exists.

A sensible split: free stock photos for blog posts, social graphics, and internal work; paid or commissioned photography for money pages, ads, and brand campaigns.

The Same-Photo-Problem and How to Check

Pexels and Pixabay share a corporate parent, and many creators upload everywhere. The result: the same photo appears on multiple sites, sometimes under slightly different license text. Before you invest design time in an image, check who else uses it.

1. Save the image file.
2. Run a reverse image search. Google Images, TinEye, and Bing Visual Search all work. TinEye sorts by oldest first, which helps you find the original source.
3. Look at the results. A handful of blog usages is normal. A photo on fifty landing pages in your exact niche will read as generic to your visitors.
4. If the original source is a photographer’s own site, read their terms there. Aggregator copies can lag behind a license change.

This step takes two minutes and prevents the worst outcome: your hero image matching your competitor’s.

Choosing Photos That Do Not Look Generic

Catalog algorithms push the same popular files to everyone. Push back with selection criteria:

• Specific over symbolic. A real workshop with worn tools beats a white-gloved hand holding a wrench. Specificity signals authenticity.
• Natural light and imperfect framing. Overly polished, perfectly centered shots read as stock. Slight asymmetry reads as documentary.
• Faces doing something. Smiling-at-camera portraits are the single most overused category. People working, concentrating, or mid-conversation feel real.
• Color harmony with your brand. Filter candidate downloads by palette before you commit. A technically great photo in clashing colors weakens the page.
• Check the timestamp. Fashion, devices, and interiors date fast. A 2015 phone in a 2026 article undermines trust.

Keep a shortlist of two or three photographers whose style fits your brand, then browse their portfolios directly instead of searching the whole catalog.

Editorial Versus Commercial Use

Classify each project before you pick a file:

The common trap: treating “my blog is not a shop” as non-commercial. If the blog promotes anything, courts and platforms treat it as commercial use. Pick files licensed for commercial use regardless of how small the site is.

Model and Property Releases: The Basics

A release answers one question: did the subject agree to commercial use of their likeness or property?

• Photos from paid agencies list release status on the asset page. Trust that label.
• Free sites rarely state release status. Assume none exists unless stated.
• Absence of a release blocks implied endorsement, sensitive topics (health, finance, politics), and advertising use featuring the person prominently.
• Editorial use of the same photo usually stays safe because editorial contexts describe reality rather than sell through it.

Practical rule for free images: if the person’s face carries the message of your ad, either get a released version or change creative direction.

Part Two: Optimize Everything You Download

Here is the part most teams skip. Stock downloads ship oversized because they must serve every use case, from a full-screen wallpaper to a thumbnail. A typical Unsplash original measures 6000 by 4000 pixels and weighs 8–15 MB as JPEG. Your blog slot needs 1200 pixels wide and under 150 KB. Serving the original wastes roughly 98% of the bytes and drags down Largest Contentful Paint.

Treat every download as raw material and run it through this pipeline.

Step 1: Resize to Actual Display Size

Open your layout and measure the rendered width. Multiply by 2 for retina screens. That number, plus a small safety margin, is your export width.

# ImageMagick: resize a 6000px original to 1600px wide
magick input.jpg -resize 1600x output.jpg

Never rely on CSS to shrink a giant image. The browser still downloads every byte first. If you serve many sizes, write responsive markup with srcset so each device pulls its own size.

Step 2: Convert to WebP or AVIF

Modern formats cut file size another 25–50% at equal quality. Convert the resized file:

# cwebp at quality 80, the usual sweet spot for photographic content
cwebp -q 80 output.jpg -o output.webp

AVIF compresses further and suits hero images where every kilobyte counts, though encoding takes longer. Our guides on reducing image file size and converting to WebP cover the settings in depth, including when lossless conversion wins.

Serve the modern format with a fallback so older browsers keep working:

<picture>
  <source srcset="hero.avif" type="image/avif">
  <source srcset="hero.webp" type="image/webp">
  <img src="hero.jpg" alt="Team collaborating in a sunlit studio" width="1600" height="900">
</picture>

Note the explicit width and height. They reserve layout space and prevent cumulative layout shift while the image loads.

Step 3: Compress With Intent

Quality 75–85 handles most photographic content invisibly. Below 70, watch for banding in skies and blur around text within the photo. Compare the compressed result against the original at actual display size, not zoomed in. Our free image tools roundup lists converters and compressors that cost nothing.

If you process many downloads at once, script the whole pipeline so nobody skips steps:

#!/bin/sh
# Resize, convert, and clean up in one pass
magick "$1" -resize 1600x /tmp/stock_tmp.png
cwebp -q 80 /tmp/stock_tmp.png -o "${1%.*}.webp"

Step 4: Strip What You Do Not Need

Stock files often carry embedded profiles, camera EXIF data, and thumbnails. Stripping metadata trims a few percent and removes location data. One caution: some licenses ask you to keep embedded credit metadata when present. Check before you strip attribution fields from CC-BY files.

Hosting Optimized Stock Libraries on a CDN

Teams that reuse a shared set of approved stock images should host them once, optimized, instead of letting every project re-download originals. A CDN gives you one canonical URL per image, automatic format negotiation, and cache headers that survive redesigns.

Sirv handles this pattern end to end: upload your trimmed, approved library, and Sirv serves WebP and AVIF automatically, resizes on demand, and delivers from edge locations. The Sirv Media Viewer adds galleries, zoom, and 360 spins when a stock set doubles as product imagery. You can create a free account and point your pages at the CDN URLs within minutes. Pair this with our guide on image caching headers for long-lived assets.

Attribution Bookkeeping

Mandatory credits rot. Someone redesigns the footer, the credit vanishes, and the violation sits unnoticed for years. Make attribution a tracked field, not a comment in a design file.

The spreadsheet approach

Columns that hold up in practice:

Review the sheet twice a year. Filter on Attribution needed = Yes and confirm each credit still renders somewhere near the image.

The CMS-field approach

If your CMS supports custom fields, move the same columns onto the media item itself: license_name, credit_line, source_url. Then render the credit line automatically wherever attribution is required. Automation beats discipline; a template that prints credits cannot forget them.

For CC-BY specifically, a compliant credit names the creator, links to the source, links to the license deed, and notes any edits. Example: “Photo by Dana Reyes (CC BY 4.0), cropped.”

A Checklist You Can Run on Every Image

1. License allows your exact use, including commercial scope.
2. No identifiable person implies endorsement; releases exist where claims demand them.
3. No trademarked objects carrying the message.
4. Reverse search shows acceptable saturation.
5. Resized to displayed dimensions times device pixel ratio.
6. Converted to WebP or AVIF with a fallback.
7. Compressed to the smallest size that survives visual inspection.
8. License recorded in the spreadsheet or CMS field, with credit pre-written.
9. Deployed from a CDN URL that will outlive the current project.

Wrapping Up

Free stock photos give small teams imagery they could never commission. The license landscape looks intimidating but reduces to four questions: what does this specific license say, does my use count as commercial, does anyone in the photo need a release, and do I owe a credit. Answer those once per image, record the answer, and the legal side stays clean.

The technical side is simpler still: never ship a stock download untouched. Resize to what the page shows, convert to WebP or AVIF, compress deliberately, and host the survivors on a CDN. Your pages get faster, and your future self inherits a tidy, documented library instead of a folder of 12 MB mysteries.