How Leopar attributes Unsplash photos

This page is live proof for the Unsplash partnerships team. Everything below is produced by the same code that runs on every website Leopar generates. Hover any photographer name to see the UTM link in your browser's status bar.

1. What Leopar does with the API

Leopar builds a website for a small business from a one-sentence description. When the generated page needs a photograph (a hero image, a section illustration), our server calls GET /search/photos, caches the result for 90 days, and inserts the photo into the customer's page. Photos are never re-hosted or modified.

Roughly 5 to 10 photos per generated website.
Generated pages reference https://leopar.io/img?q=…&i=…, which answers with an HTTP 302 redirect to the photo's own images.unsplash.com URL. The browser therefore loads the image from Unsplash, not from us. We use this indirection only so that a generated page keeps working if a photo is later replaced.
GET /photos/:id/download is called on every redirect, so every real display is reported, as the guidelines require.
No filtering, cropping or editing beyond CSS object-fit framing.

2. The attribution, exactly as visitors see it

Each credit names the photographer, links to their Unsplash profile, names Unsplash, and links to unsplash.com. Both links carry utm_source=leopar&utm_medium=referral.

Photo : Yeh Xintong / Unsplash

Photo : Oxana Melis / Unsplash

Photo : Mike Kenneally / Unsplash

3. The HTML we generate

This is the literal markup of the first credit above, copied from the page you are reading:

Photo : <a href="https://unsplash.com/@blsnki?utm_source=leopar&amp;utm_medium=referral" target="_blank" rel="noopener">Yeh Xintong</a> / <a href="https://unsplash.com/?utm_source=leopar&utm_medium=referral" target="_blank" rel="noopener">Unsplash</a>

4. Where it appears on a customer website

The credits sit in the footer of every generated page, one line per distinct photograph, and they remain in place when the customer's site goes live on their own domain and server. They are part of the generated document, not an overlay that can be dismissed.

A generated example is available on request; this page uses the identical credit function (leopar_image_credit_html()), so the output is byte-for-byte the same.

4b. Reviewer portraits

Customer-review sections show a small round portrait next to each first name. These come from a FIXED set of twelve Unsplash portraits (config/avatars.json), hot-linked from images.unsplash.com with Unsplash's own face crop, and credited in the footer exactly like the other photographs. Their download_location endpoints were triggered when the set was selected.