Mobile game session replay

See the session.
Understand the exit.

Watch what happened inside a hosted playable demo, then add touch and pointer context when you need to understand why.

Charts can show that a player stopped, retried, or left. Session replay shows the experience around that moment. PixelPicked records a lightweight view of supported hosted game canvases and keeps interaction data separate, so developers can watch a clean replay, toggle visible inputs, and inspect the session without adding a replay SDK to the game.

From a metric to the moment behind it

Watch behavior.
Keep the context.

Replay is connected to the same hosted session as analytics, performance signals, and player feedback.

  • 01

    Canvas session recording

    Capture a lightweight visual replay of supported browser-playable game canvases while a player uses the PixelPicked demo.

    Gameplay replay
  • 02

    Optional input overlay

    Toggle recorded taps and pointer positions over the video to see where the player interacted without changing the original game session.

    Touches and clicks
  • 03

    Session context

    Review replay alongside duration, device details, frame-rate information, errors, and the other signals available for that session.

    Performance context
  • 04

    Downloadable replay

    Export a replay with PixelPicked attribution and, when selected, the visible interaction overlay for review or sharing with the team.

    Replay export

Designed for useful, bounded capture

Record less noise.
Find useful sessions.

Replay focuses on the hosted game canvas rather than recording the player's phone or the rest of the browser.

  • 05

    Automatic capture

    Eligible hosted demo sessions can be recorded automatically, so developers do not need to ask each player to start a recording.

    No replay SDK
  • 06

    Game canvas only

    Replay is limited to the supported hosted game canvas. It does not capture the player's camera, microphone, other tabs, or the rest of the device.

    Scoped capture

Example replay investigation

Find the drop-off.
Review the sequence.

Replay is most useful after aggregate analytics identifies a session or moment worth investigating.

  • 07

    Filter to the affected sessions

    Start with a build, device, performance issue, error, unusually short session, or progression drop-off instead of watching recordings at random.

    Find the signal
  • 08

    Watch the clean gameplay view

    Review the recorded canvas first to understand the visible sequence without interaction markers covering the game.

    Replay
  • 09

    Toggle touches when needed

    Enable the separate input overlay to check whether the player tapped the expected control, repeated an action, or interacted somewhere unexpected.

    Input context
  • 10

    Compare before changing the build

    Check similar sessions and aggregate signals before treating one replay as representative. A recording supplies context, not statistical proof by itself.

    Validate

Common questions

Everything you
need to know.

Does mobile game session replay require an SDK?

No additional replay SDK is required for supported HTML builds hosted on PixelPicked. Capture is provided by the PixelPicked play environment.

Does replay record the player's whole screen?

No. Replay is scoped to the supported hosted game canvas and does not capture camera video, microphone audio, other tabs, or content outside the hosted game.

Can I see where the player tapped?

Yes. Recorded touch or pointer positions can be displayed as an optional overlay during playback and included when a compatible replay is exported.

Which games support session replay?

Session replay applies to supported browser-playable HTML builds hosted on PixelPicked. Availability and recording quality can vary with the game canvas, browser, and device performance.

Use aggregate analytics to find the pattern, then open the sessions that explain it.

Measure. Replay. Improve.