Embed a controller tester on your site. Build the iframe below, copy it, done.

Four JoyCheck instruments can run on your own site with a single iframe. No API key, no account, no script tag, and no tracking code. Build the snippet in the embed builder above, copy it, paste it into any HTML block.

4 widgets · up to 10 languages · zero dependencies · 4 min read

These are the same instruments that run on JoyCheck itself, served from a stripped-down route with no navigation, no footer, and no analytics. An embed runs inside your page, so it fires no tags and sets no cookies of its own in your readers’ context.

Updated on 2026-08-10 by Taimoor Bamazai, founder of Elites Algorithm (Dublin, Ireland and Pakistan), and the builder behind JoyCheck.

Which widget do you need?

Three instruments, offered as four choices, because the console comes in two sizes. The five stick-and-button tool pages on JoyCheck all run one engine, and the input analysis console is its face; the polling rate test and the wheel tester are separate instruments with their own layouts.

Every height above was measured in a browser, not estimated. They are starting points: a narrower column makes each instrument taller, because the panels reflow into fewer columns. At phone width the full console runs past 5,000 pixels, while the compact one settles near 1,780.

Full or compact?

They are one widget at two sizes — the same route, the same design, the same behaviour. ?layout=compact hides the two stacked readout blocks underneath the instrument: the diagnostic panel cards and the advanced diagnostics grid.

That choice is about the page, not the reader. Give a hardware review or a drift troubleshooting guide the full console: the tester is the page, and the numeric panels are what the reader came to read. Give a buying guide or a how-to the compact one, where a 3,000-pixel instrument would bury the writing.

Nothing becomes untestable in compact form. Sticks, triggers, D-pad and face buttons are all live on the instrument; vibration is driven from the toolbar; calibration, the health score and the drift verdict all stay. What goes is the numeric readout beside them. The advanced-diagnostics button is hidden along with the section it opens, rather than left on screen doing nothing.

Letting the widget size itself

Guessing a pixel height is the single most common way an embed ends up looking broken, because the right number changes with your column width, and your column width changes with the reader’s screen.

Tick auto-fit height in the builder and the snippet gains a short listener. The embed then reports its own height to your page whenever it changes, and the frame follows:

<script>
  window.addEventListener('message', function (e) {
    if (e.origin !== 'https://joycheck.io') return;
    if (!e.data || e.data.type !== 'joycheck:height') return;
    var f = document.querySelectorAll('iframe[src*="/embed/"]');
    for (var i = 0; i < f.length; i++) {
      if (f[i].contentWindow === e.source) f[i].style.height = e.data.height + 'px';
    }
  });
</script>

Three things are worth knowing about it. It matches frames by contentWindow rather than by id, so one copy of the listener drives however many JoyCheck widgets a page carries. The traffic is one-way: the embed registers no message listener of its own, so nothing on your page can drive the widget, and the only thing that crosses the frame boundary is an integer. And it is strictly opt-in, because the auto-fit URL carries ?fit=1 — every snippet copied before this existed keeps behaving exactly as it did.

Loading a widget in another language

Append ?lang= and a two-letter code. English is the default, so no parameter is needed for English, and the builder writes the parameter for you.

Both sizes of the input analysis console ship ar, de, es, fr, id, ja, pt, ru and tr alongside English. The steering wheel tester ships ar, de, es, fr, pt and tr. The polling rate test ships none: it carries no translation dictionary, so a language parameter on it would change nothing, and the builder disables the control rather than pretend otherwise.

Arabic switches the widget to a right-to-left layout on its own.

What these embeds deliberately do not do

Four limits, stated plainly rather than discovered later.

No analytics, no cookies of our own. The embed routes load no tag manager, no analytics, and no advertising code, and set nothing themselves. This differs from the main JoyCheck site on purpose: your page is not ours to instrument. The one caveat worth stating: a reader who has used joycheck.io directly already has that domain’s analytics cookies, and those ride along with the embed request unless their browser blocks third-party cookies. Nothing new is set and nothing reads them.

No theme switching. The instruments render in JoyCheck’s dark palette regardless of your site’s theme — and regardless of JoyCheck’s own, since the site has a light mode and the instruments stay dark there too. On a light page they read as a self-contained panel, the way an embedded video player does. That is why the builder has no theme control: a switch that changed nothing would be worse than the limitation.

No force feedback in the wheel widget. Most wheels expose no rumble actuator to the browser at all, so the steering wheel tester reports that capability honestly instead of simulating a test. The same limit applies embedded.

No link equity. An iframe is not a link, so embedding JoyCheck passes no ranking signal in either direction. What it does give you is a working tool on your page, and what it gives us is the attribution link in the corner. Both sides should embed for that reason and no other.

If you already embedded the older tester

The route at https://joycheck.io/embed/gamepad-tester/ carries the previous tester skin. It is still built, still served, and renders exactly what it always did — an embed already on your page will not change under you, and there is no date on which it stops working.

It is simply no longer what the builder hands out. That skin is a design generation behind the console, so offering both made the picker look like two different products rather than two sizes of one. If you would like the newer look, the compact console is the closest replacement, and swapping is a one-line change to the src.