Skip to main content
Localhost Environment

How to Handle Screenshots and Replays in a Localhost Setup

Joe Scanlon avatar
Written by Joe Scanlon
Updated over a month ago

Are you facing challenges with screenshots and session replays when using Marker.io in a localhost environment? This guide walks you through the common issues and provides simple solutions to ensure you capture all necessary details and interactions effectively.


Taking Screenshots in a Localhost Environment

When working on a localhost, you might encounter problems capturing screenshots due to our server-side renderer's limitations in accessing local files, especially images. This can result in errors or delays. Here’s how you can effectively capture screenshots in your localhost environment:

  1. Install the Browser Extension: Use the Marker.io Browser Extension, which allows you to capture screenshots, including local images.

  2. Use the Native Browser API: Alternatively, leverage the browser's built-in screenshot capabilities.

By using either of these methods, you'll ensure that your screenshots include the necessary elements from your localhost environment, even when our server cannot access them.


Session Replay on localhost

Session replays in a localhost environment present a different set of challenges. Our server cannot access local images, which can impact the display of session replays. Here’s what You’ll Experience with Session Replays:

  • Accurate Event and Interaction Tracking: All user interactions, such as clicks, form submissions, and other events, will still be captured and recorded accurately, ensuring that your session replays reflect user behavior correctly.

  • Broken Images: Since our server cannot access images stored locally, you may notice broken images or missing visuals in your session replays.

Unfortunately, there's no workaround for capturing local images during session replays at this time. To achieve full functionality, including correct image rendering, we recommend conducting tests in a live environment instead of localhost.


Need Help?

If you have any questions, comments, or corrections, chat with us at the bottom right of our web pages.

Did this answer your question?