Bring your website.
Upload a ZIP or folder of static files, or start from a public website URL. No recipient installation needed.
FROM WEBSITE TO HANDS-ON
One link.
A working experience.
Share a website through a remote browser. Your visitor interacts with the experience while you manage the frame.
Set the opening scene.
Choose where the preview starts. Set when it can be opened, limit session time and create temporary viewer passwords.
Share the experience.
Send the short link. Visitors click, type and touch the remote view. Review their viewing sessions in your workspace.
Start with a URL or a static build.
For an existing website, create a frame from a public HTTP or HTTPS URL. The remote browser loads the website from its host. For a private prototype, upload a ZIP or folder containing HTML, CSS, JavaScript and local assets. Compare URL frames and uploaded builds before choosing.
Open it exactly where it matters.
Choose a launch path such as /?demo=1 or /index.html?mode=demo#start for an uploaded build. Framevault opens that path inside the remote browser. Your own localhost server does not need to stay running.
Give each review a clear window.
Set the frame’s availability and session time limit. Use a reusable viewer password or issue temporary one-time passwords when a new session should require a fresh credential. Learn how temporary preview access works.
Natural interaction, not another text box.
Visitors click, type, paste plain text, scroll, and use touch controls inside a responsive viewer. A short disconnect can reconnect to the same remote browser within the configured 30-second grace period. Remote viewing uses the frame owner’s allowance.
Understand the runtime.
Uploaded builds must be self-contained static websites. Uploading a backend process does not start a server, and external API, CDN and WebSocket access is blocked for uploaded builds. Bundle the resources needed for your demo. URL frames access supported public websites; private network addresses are not supported and some websites may block remote browsers.
Test demanding graphics before sharing.
WebGL graphics run on the renderer service, not your visitor’s GPU. Software rendering performance depends on the build, canvas size, service CPU and memory. Test heavy games and graphics before sending the link to an audience.
Follow up with context.
Your workspace brings together viewing activity for each frame, including session times and duration. Read the preview analytics guide to understand the available visitor information and its limits.