ExerciseDB GIFs: how to buy and embed them

The marketplace at fitexercisedb.com/marketplace sells the 1,324 exercise demonstration GIFs as individual assets, browsable by body part (Upper Arms, Back, Waist, Chest, and so on). Each listing shows a watermarked preview, the exercise name, target muscle and equipment, and a $0.99 add-to-cart button. Checkout runs through Stripe; the file you receive has the watermark removed.

This is separate from the API plans, which are for structured exercise data, not images.

No. A call to GET /v1/exercises/{id} returns the exercise's name, body part, target muscle, equipment, MET value and instructions, the same fields the calorie calculation post works from. It does not return an image file or a hosted GIF URL. What it does include is a _links.marketplacePreview entry pointing at the matching marketplace listing:

{
  "id": "0001",
  "name": "3/4 Sit-up",
  "bodyPart": "Waist",
  "_links": {
    "self": { "href": "/v1/exercises/0001" },
    "related": { "href": "/v1/exercises/0001/related" },
    "calories": { "href": "/v1/exercises/0001/calories{?bodyweightKg,minutes}", "templated": true },
    "marketplacePreview": { "href": "/marketplace/preview/0001.gif" }
  }
}

So an app can show the metadata straight from the API and link out to the marketplace for the visual, or buy the asset separately and host it itself.

The single-asset price makes sense for a handful of exercises: a landing page hero, a few program illustrations. Beyond that, buy a pack: a group of exercises sharing a body part, equipment or target muscle is discounted by size, and the price is capped at the full-library bundle.

The license is royalty-free for one project: you can use the GIF in an app, website or printed material for that project without further payment. It does not include resale, redistribution as a standalone asset, or reuse across multiple unrelated products. If you are building a fitness app that will ship the GIFs alongside its own paid subscription, that is the intended use; reselling the raw files as your own asset pack is not.

Once checkout delivers the clean file, host it yourself rather than linking back to the marketplace preview (that URL is a watermarked preview, not a stable asset link). A few practical points:

• Give the <img> a real alt describing the movement, not the filename, both for accessibility and because it is what a screen reader or a language model reads back.
• A 1,324-exercise GIF library adds up in file size. For exercises shown in a list or feed rather than full-screen, converting the GIF to a short muted video (MP4 or WebM) cuts the payload substantially without losing the loop, a swap web.dev recommends for any looping animation.
• Lazy-load anything below the fold; a workout list with 20 exercises does not need to decode 20 animations before the user scrolls to them.

Yes: packs and the bundle. A pack is discounted 40% under 25 GIFs, 55% from 25 and 65% from 100, and never costs more than the bundle. The bundle is $393.23 for all 1,324 exercises against $1,310.76 one at a time, so it only wins once a project needs a very large share of the library. If the goal is exercise data rather than visuals, that is a different product entirely: the API plans start at $9/month for 100 requests a day and return the same metadata structure covered in the MET and calories post, with a free tier at 10 requests a day and no card required.