What does recording look like for my visitor?

They click your button and a small widget appears in the corner of the page. They choose screen, or screen plus camera, the browser asks for screen-share permission, and a timer with a stop button appears while they record. When they stop, the recording uploads and the widget thanks them and gets out of the way. Your page stays usable throughout.

Do my users need a Pixelmatic account?

No. Only your team does. The person recording just needs a browser and your web page.

Where do the recordings go?

Into your organisation's library, unpublished, where your team can watch, share, transcribe, and search them like any other recording. They only get a public page if the API key carries the Auto-publish permission, which is off unless you tick it.

Can I tell who made a recording?

Yes. The embed accepts a user object (id, email, name) and any metadata you want to attach, straight from your own app. The page URL and browser are captured automatically.

Is it safe to put the API key in my HTML?

The key only works from the domains you list on it, and only for the permissions you tick. A recording-only key can't search your library or publish anything. Requests are rate limited per key, and you can cycle or revoke a key at any time from Settings → Integrations.

Desktop browsers with screen-sharing support, which today means current Chrome, Edge, Firefox, and Safari. Mobile browsers generally don't allow web pages to capture the screen, so treat the widget as a desktop experience.

Pixelmatic

Start recording, free

Embeddable recorder

Let your users show you.
Right from your app.

One script tag puts a screen recorder behind any button on your site or web app. Visitors record their screen and talk it through, and the video lands privately in your library, with their name attached if you want it. Nothing for them to install, no account to make.

Start your 14-day trial Try the recorder, free

14 days free. No card required. Unlimited teammates on every team plan.

The problem

They saw it happen.
You got a paragraph about it.

"Steps to reproduce" written from memory.: The bug report says one thing, the screen said another. By the time it reaches you, the details that mattered are gone, and the round trips begin.
Support tickets describe what a video would show.: Your customer types three paragraphs about what they're seeing. Your agent asks for a screenshot. Then another. A 40-second recording would have ended the thread before it started.
Feedback tools ask too much of the person giving feedback.: Install an extension, create an account, upload a file somewhere. Every step loses people, and the ones you lose are exactly the ones who would have shrugged and moved on.
The context lives on their machine, not yours.: Which page, which browser, which account, what data was on screen. You can't see any of it, so you guess. Guessing is slow.

How it works

A recorder on your site, a library on ours.

One script tag, any button: Paste the snippet and mark up a button, or call the JavaScript API from your own code. That's the whole integration. The recorder opens when your user clicks, on any page of your site.
A small widget, not a takeover: The recorder sits in the corner of the page: a compact picker, then just a camera bubble and a timer while recording. Your site stays visible and usable the whole time.
Nothing for your visitor to install: Recording runs on the browser's own screen sharing, straight from your page. No extension, no download, and no Pixelmatic account for the person recording.
Private by default: Recordings land in your library unpublished, visible to your team only. Publishing to a public page is a separate permission you grant per key, deliberately.
You know who recorded, and from where: Pass the user's name, email, and any metadata from your app, and it's stored with the recording. The page URL comes along automatically, so "where did this happen" answers itself.
Keys you control: The same API keys that power public search. Each key carries permissions and a domain allowlist, is rate limited, and can be disabled, cycled, or deleted the moment you want it gone.

What this opens up

Anywhere "just show me" beats "please describe".

A "Report a problem" button in your app, and bug reports that show the bug
A support portal where customers show you what they're seeing instead of describing it
Client feedback on staging sites, collected by agencies without another tool
UAT rounds where testers narrate what broke as it breaks
Testimonials and video answers gathered from a simple page you control
Customer research where users walk you through their workflow in their own words

Frequently asked questions.

Put a record button
on your site or app.

Create a key, paste the snippet, and click your own button. The first recording takes minutes, and it arrives with everything a written report leaves out.