The calculator, on your site.

Embeddable calculator

The iframe fills its container and everything it runs happens on our domain, so your page loads no JavaScript of ours. The recommended height is 1560px. Under 640px of width the form drops to a single column and the block grows to about 2200px, so in a column that narrow linking the calculator is usually the better option.

Embedding makes sense in an article of your own where the reader is already thinking about rates — a guide, a media kit, a resources page; linking works better in a bio, an email or a sales landing, where the iframe competes with the main message. All three blocks update themselves: the figures come from the same dataset as the calculator, so there is no code to copy again when a CPM changes. The badge keeps the link and the attribution, and the citation keeps the academic format with the dataset's revision date.

All three blocks can be used on a commercial site without asking: the dataset is open under CC BY 4.0 and the widget only asks that the attribution and the link stay in place. There is no published request quota because the widget is served as static HTML; if your page gets heavy traffic and you want the whole dataset, the CSV is the recommended route and has no limit.

<iframe
  src="https://creatorrates.app/embed/calculator"
  title="Sponsorship rate calculator"
  width="100%"
  height="1560"
  style="border:0"
  loading="lazy"
></iframe>

• The “Free calculator by CreatorRates” line lives inside the widget and links back here. That is the only condition: do not cover it or remove it.
• The widget follows the reader's theme: if their system is dark it renders dark, and the three icons next to the attribution — auto, light, dark — let them pin it. It is the same preference as on creatorrates.app, so the choice carries over from the widget to the site.
• For Spanish sites there is the same widget with the attribution in Spanish: /embeds.
• If you would rather link than embed, the calculator is at /en/calculator.

Dataset badge

A 220 × 52px SVG served from our domain with a long cache: it weighs almost nothing and you do not have to host it. The link to the dataset is in the snippet, because an image on its own is not a link.

<a href="https://creatorrates.app/en/data"><img src="https://creatorrates.app/api/badge/cpm.svg" alt="Creator CPM 2026 · CreatorRates" width="220" height="52"></a>

Data citation

If you are after the figures rather than the calculator, this is the reference. The dataset is published under a CC BY 4.0 licence, so you may copy and reuse it — commercially too — as long as you credit the source.

The licence and the endpoints are on open data; where the numbers come from is documented in the methodology.

What you can and cannot do

• Yes: embed it in an article, a resources page, a classroom or a product's documentation. Linking to it or quoting the figures is fine too.
• No: removing the attribution, covering it with your own styles or presenting the widget as your own.
• No need to ask. If you want us to know, one email is enough — and it saves us finding out by chance.
• The figures are not editable: if a number does not fit your article, checking the methodology is more useful than changing it inside the iframe.

Before you publish: three checks

The snippet is one line, but a badly placed embed does not fail in the console — it fails for the reader. These are the three things worth checking before you call the page done.

• The height. The iframe does not resize itself. 1560px covers the real widget in two columns; under 640px the form drops to a single column and grows to about 2200px, so inside a mobile container the block gets cut off. Check it at 390px wide: either raise the attribute to 2200, or replace the iframe with a link to the calculator.
• Your own policy. If you serve a Content-Security-Policy, the iframe will not load until you allow the origin: add frame-src https://creatorrates.app. Without a CSP this step does not apply.
• The attribution. The line lives inside the iframe and is served from our domain, so your CSS cannot cover it; what can clip it is a container with overflow: hidden and a height shorter than the block. If it looks cut, the problem is the height, not the snippet.

What happens when the figures change

The widget keeps no copy of the dataset: it reads the published references every time it loads, so a catalogue revision reaches your page without you touching anything. An article that quotes frozen figures ages just as fast — it simply does not update itself. The combination that holds up is the iframe for the live number plus one sentence naming the dataset's revision date, so the reader knows when it was measured: that date is in the citation and on the open data page.

If you publish a study comparing 2026 CPMs with 2025, cite the CSV with its date rather than the widget alone: a downloadable table lets the reader check the series, while the iframe only shows today's value. Both can be cited under the same licence, so there is no need to pick one over the other.