Unsplash Was Great. What Comes Next?

Unsplash did something remarkable: it made high-quality stock photos genuinely free, genuinely accessible, and genuinely good.

For about a decade, it was the default answer to "where do I get images for my project?" Designers used it for mockups. Developers integrated its API into apps. Startups launched with Unsplash heroes. The photography was real, the license was permissive, and the API was a dream to work with.

Then Getty acquired it. And things changed. (For the full industry landscape, see The State of Stock Photography in 2026.)

What Unsplash got right

Before we talk about what went wrong, let's acknowledge what went right. Unsplash understood something important:

Friction kills usage. No accounts required to browse. No watermarks. No "request quote for pricing." You found an image, you downloaded it, you used it. Done.

The API was first-class. Unsplash treated developers as a real audience. The API was well-documented, reliable, and free for most use cases. Thousands of apps integrated it: image pickers, design tools, content platforms, placeholder services.

Community created supply. Photographers contributed because they got exposure. Users got free images. The flywheel worked. Quality was high because contributors cared about their portfolios.

The license was clear. No attribution required (though appreciated). Commercial use allowed. No "editorial use only" asterisks. You could actually use the images without a legal review.

This combination (quality, access, API, license) made Unsplash the obvious choice for a generation of developers and designers.

What happened after Getty

Getty acquired Unsplash in 2021. For a while, things seemed stable. Then the changes started:

The API got restricted. Rate limits tightened. New applications faced longer approval times. Some integrations stopped working.

The Source endpoint died. The beloved source.unsplash.com, which let you embed random images by keyword with a simple URL, was deprecated and eventually shut down. Thousands of projects broke.

The SDK was archived. The official JavaScript SDK stopped being maintained. Pull requests sat untouched. Issues piled up.

Pricing appeared. Enterprise tiers. Usage limits. The "free forever" promise started feeling conditional.

None of this was evil. Getty is a business; they paid money for Unsplash; they're entitled to monetize it. But the product that developers fell in love with, the frictionless, API-first, genuinely free image source, slowly became something else.

The vacuum

Today, if you're a developer building something that needs images, your options are:

Use Unsplash anyway. It still works. The API still exists. But you're building on a platform that's clearly de-prioritizing developer experience. How long until the next breaking change?

Use Pexels. Similar model, still free, still has an API. But the library is smaller, the curation is weaker, and it's owned by Canva, so the same acquisition dynamics could play out.

Pay for stock. Shutterstock, Adobe Stock, Getty proper. Works if you have budget. Doesn't work if you're building a side project, a startup MVP, or a tool that needs to embed images for users.

Use AI generation. Services like Midjourney, Nano Banana, or Stable Diffusion. Powerful, but you're generating on-demand, which means cost per image, latency, and no guarantee of consistency.

None of these fully replaces what Unsplash was at its peak: a free, fast, API-first library of quality images that just worked.

What comes next

We built OKSLOP to fill this gap. Not as an Unsplash clone, but as something different that serves similar needs.

Free tier that's actually free. No watermarks. No "sign up to download." No usage limits that make the free tier unusable for real projects.

API-first design. We assume developers are a primary audience. The API is documented, stable, and designed for integration. Deterministic image URLs (same seed = same image) for predictable embedding.

Semantic search. You search for concepts, not keywords. "Cozy workspace with plants" returns relevant results even if no image was manually tagged that way. (The migration guide has code examples.)

AI-generated, honestly labeled. Our images are AI-generated, and we don't hide it. The name is the disclosure. No pretending to be photography; no uncanny valley surprises.

Growing library. Traditional stock is a fixed catalog. Our library grows with every brief submitted. Popular vibes get more coverage. The search gets better as usage increases.

For developers specifically

If you integrated Unsplash's API, here's what OKSLOP offers:

• Simple REST API with predictable endpoints
• Responsive variants with multiple sizes per image, CDN-delivered
• Deterministic URLs so the same image ID = same image forever, no randomness surprises
• No API key for basic access so you can start building before you sign up
• SDK in progress with React components, Next.js helpers, more coming

We're building for the use case Unsplash used to serve: developers who need images in their apps without enterprise contracts or per-download fees. If you're ready to switch, here's how to migrate in 10 minutes.

The honest trade-off

OKSLOP isn't a drop-in replacement for Unsplash. The libraries are different. The aesthetic is different. And the images are AI-generated, not photographed.

For some projects, that matters. If you specifically need photographs of real places, real people, real moments, AI images won't cut it.

For other projects, it doesn't matter at all. A blog needs a hero image. An app needs placeholder content. A landing page needs something better than lorem ipsum. For these use cases, whether a human held a camera is less important than whether the image works.

We're honest about what we are. That honesty is the product.

The future of free images

Our bet: the future of free, accessible images is AI-generated. Not because AI is better than photography. It's not, and we're not shy about saying so. But photography can't be free at scale. Photographers need to eat. Stock libraries need to pay them. Someone funds the production, and that cost gets passed to you.

AI generation breaks that loop. Pre-generate, share infinitely, amortize costs across all users. A free library becomes sustainable through different economics, not through anyone working for free.

That's what comes next. Not "Unsplash but cheaper." A different model that serves similar needs in a different way.

Getting started

If you're looking for an Unsplash alternative:

• Browse the library at okslop.com
• Check the API docs for integration details
• Search semantically: describe what you want, not just keywords
• Download free, use commercially, no attribution required

Unsplash was great. It changed how a generation of developers thought about image access. What comes next will be different, but hopefully just as useful.