Link to ProbeCheck

Help your visitors test their devices — link to ProbeCheck or embed our tools directly. Copy ready-to-use HTML, Markdown, badges, and iframe snippets below.

Text Links

Copy and paste these links into your blog posts, documentation, or support pages.

Homepage
<a href="https://probecheck.com">ProbeCheck — Free Online Device Diagnostics</a>
Webcam Test
<a href="https://probecheck.com/webcam-test">Free Webcam Test Online</a>
Microphone Test
<a href="https://probecheck.com/mic-test">Free Microphone Test Online</a>
Keyboard Test
<a href="https://probecheck.com/keyboard-test">Free Keyboard Test Online</a>
Screen / Dead Pixel Test
<a href="https://probecheck.com/screen-test">Free Screen & Dead Pixel Test</a>

Markdown Links

For GitHub READMEs, wikis, and Markdown-based documentation.

[ProbeCheck](https://probecheck.com) — free online device diagnostics
[Webcam Test](https://probecheck.com/webcam-test) | [Mic Test](https://probecheck.com/mic-test) | [Keyboard Test](https://probecheck.com/keyboard-test)

Badge

Add a badge to your site or README. Right-click to save the image.

ProbeCheckDevice Diagnostics
Dark badge (PNG)
ProbeCheckDevice Diagnostics
Light badge (PNG)
Markdown with badge
[![ProbeCheck](https://probecheck.com/badge-dark.svg)](https://probecheck.com)

Embed Widget

Embed the full ProbeCheck tool directly in your site using an iframe.

Webcam Test
<iframe src="https://probecheck.com/webcam-test" width="100%" height="600" frameborder="0" loading="lazy" title="Webcam Test — ProbeCheck"></iframe>
Microphone Test
<iframe src="https://probecheck.com/mic-test" width="100%" height="600" frameborder="0" loading="lazy" title="Microphone Test — ProbeCheck"></iframe>
Keyboard Test
<iframe src="https://probecheck.com/keyboard-test" width="100%" height="600" frameborder="0" loading="lazy" title="Keyboard Test — ProbeCheck"></iframe>

Note: Some sites (e.g. Notion, certain CMS platforms) may block iframe embeds. In that case, use text links above.

Social Sharing

Share ProbeCheck on social media.

Twitter / XLinkedInHacker News

npm Package

Use ProbeCheck's detection engine in your own project.

npm install @probecheck/probe-engine

Package: npmjs.com/@probecheck/probe-engine

Need Help?

If you need a custom integration, specific badge format, or have questions about linking to ProbeCheck:

GitHub

Try our tools

Before linking out, run a quick test on your own device — the same tools above run entirely in your browser.

Webcam TestMic TestKeyboard TestScreen Test

Frequently Asked Questions

Can I embed ProbeCheck tools on my website?

Yes. Use the iframe snippets on this page to embed the Webcam Test, Microphone Test, or Keyboard Test directly in your site. Each iframe loads a privacy-focused tool that runs entirely in the visitor's browser — no tracking, no server-side data collection.

Do I need to attribute ProbeCheck when linking?

Attribution is appreciated but not required. You're welcome to link to any page or embed any tool. The provided text links, Markdown, and badges are designed to make integration as easy as possible for blogs, documentation, and support pages.

Are the embedded tools free to use?

Yes. All ProbeCheck tools are free, require no signup, and run entirely in the browser. You can embed them on personal blogs, commercial sites, or internal documentation at no cost.

Will embedding iframe tools slow down my site?

All embed snippets use loading="lazy" so the iframe only loads when a visitor scrolls near it. The ProbeCheck pages are static, prerendered HTML — typical load time is well under 100 KB per page.

Is there an npm package available?

Yes — the detection engine is available as @probecheck/probe-engine on npm. It bundles the same probe modules (webcam, microphone, keyboard, screen, etc.) used by the website so you can build custom device diagnostics into your own app.

How do I report an issue with the embed or links?

Open an issue on the ProbeCheck GitHub repository at github.com/yyxiong/probe-check/issues. For custom integration needs (specific badge format, alternate language, or private deployment), describe your use case in the issue and we'll respond.