Browser Support
realvirtual runs in every current browser, but a few features depend on browser capabilities that not every browser offers. The most visible one is local project folders: linking a folder on your disk and saving back into it works in Chrome and Edge only.
This page lists what works where, what the viewer does when a feature is missing, and what you can do instead. The viewer checks each capability itself at runtime (feature detection), so a missing feature is hidden or greyed out rather than failing silently.
What works in which browser
Section titled “What works in which browser”| Feature | Chrome / Edge (desktop) | Firefox | Safari (macOS / iPadOS) | Mobile Chrome / Safari | Needs HTTPS? |
|---|---|---|---|---|---|
| 3D view and simulation (WebGL 2) | Works | Works | Works | Works, starts on the Fast preset | No |
| Link or open local project folders, save back | Works | Not available | Not available | Not available | Yes (localhost counts) |
| Browser project (stored inside the browser) | Works | Works | Works | Works, with a storage limit | Yes for model files (see note) |
| Open a single GLB (file dialog, drag and drop) | Works | Works | Works | File dialog works, drag and drop depends on the device | No |
| Download and upload as fallback | Works | Works | Works | Works | No |
| Encrypted projects and password gate | Works | Works | Works | Works | Yes |
| Copy buttons | Works | Works | Works | Works | Yes, otherwise a manual-copy fallback |
| WebGPU renderer (experimental) | Works with a WebGPU adapter | Only if the browser offers WebGPU | Only if the browser offers WebGPU | Not offered on touch devices | Yes |
| Ray traced rendering | Works with WebGPU | Not supported | Not supported | Not supported | Yes |
| VR / AR (WebXR) | Works with a headset or AR device | Only if the browser offers WebXR | Only if the browser offers WebXR | Device dependent | Yes |
| Sound | Works | Works | Works, after your first click | Works, after your first tap | No |
| Video recording (MP4) | Works | Not supported | Not supported | Not supported | No |
| Cinematic video recording | Works with WebGPU and folder access | Not supported | Not supported | Not supported | Yes |
| Keep simulating in background | Works, with energy-saver limits | Works, timing not measured | Works, timing not measured | Limited by the device | No |
| Connect to CONNECT from a hosted page | Works, after a local-network permission prompt | Works if the browser allows the connection | Open the CONNECT address directly instead | Open the CONNECT address directly instead | No |
| Realtime mode (4 ms clock) | Chrome: holds 4 ms. Edge: only in the visible foreground tab | Not tested | Not tested | Not tested | No |
“Not supported” means realvirtual does not offer the feature there. It does not mean the browser is unsupported as a whole. Cells marked “Only if the browser offers…” depend on the browser version and device. realvirtual does not test them.
Notes per feature
Section titled “Notes per feature”Local project folders
Section titled “Local project folders”Linking a folder uses the File System Access API (showDirectoryPicker), which only Chrome and Edge on a desktop provide. In other browsers:
- The dashboard shows Folder projects need Chrome or Edge instead of the Add and New buttons.
- A folder action that still gets triggered answers This browser cannot open local folders.
- Pack with libraries and the old working-folder copy in Settings are hidden.
What you can do instead:
- Browser project. Create a project that lives inside the browser. It needs no folder and is writable.
- Open a GLB directly. Use the file dialog or drag the file onto the viewer.
- Export and download. Use Export .rvproject (from a folder project in Chrome or Edge) and the GLB download in the editor to move work out of the browser.
- Use a delivered build. A deployed or CONNECT-served viewer ships its own project, so nothing needs to be linked.
Browser project storage
Section titled “Browser project storage”Scenes are kept in local storage. Model files and thumbnails go into the browser’s private file system (OPFS), which needs a secure context. Without OPFS, scenes are stored but authored model files are not, and the viewer reports that it cannot store them.
Open a single GLB, download and upload
Section titled “Open a single GLB, download and upload”A standard file dialog and drag and drop work in every browser, and the file is copied into the open project. Saving works through ordinary downloads, for example the GLB download in the editor and Export .rvproject. No folder permission is involved.
Encrypted projects and password gate
Section titled “Encrypted projects and password gate”Decrypting a password-protected project uses the browser’s Web Crypto API, which exists only on HTTPS pages and on localhost. There is no software fallback for this, because the encryption itself depends on it. Open encrypted projects and verify signed content over HTTPS. A plain http:// address in a factory network works for unencrypted projects only.
Plain http in a factory network
Section titled “Plain http in a factory network”Opening the viewer from http://<hostname>/ is a normal setup. Opening projects, model files and connecting to CONNECT work there: hashing and unique IDs use built-in fallbacks. The features that need a secure context stay unavailable: folder access, encrypted projects, the browser’s private file system, the copy buttons, WebXR and WebGPU. If you need them, serve the viewer over HTTPS.
Copy buttons
Section titled “Copy buttons”Copy buttons use the Clipboard API, which needs a secure context. Where it is missing, the share dialog selects the text and asks you to copy it manually. Some other copy buttons do nothing in that case. Copy with the keyboard from the shown text.
WebGPU and ray traced rendering
Section titled “WebGPU and ray traced rendering”WebGL is the default and works everywhere. Settings → Visual → Renderer → Backend offers WebGPU (experimental) only when the browser reports a WebGPU adapter, and never on touch devices. The option is greyed out otherwise. Ray traced rendering needs the WebGPU backend, so it is limited to Chrome and Edge with a working adapter. The ray traced still image does not need folder access. The ray traced video does. See Ray traced rendering and WebGL and WebGPU.
VR and AR
Section titled “VR and AR”The VR and AR buttons appear only when the browser exposes WebXR and reports a supported session. WebXR is not available while the WebGPU backend is active; switch back to WebGL.
Sound uses the Web Audio API. Browsers, Safari above all, only allow audio after a click or tap, so sound starts after your first interaction with the page. The audio stops while the tab is hidden and resumes when you return.
Video recording
Section titled “Video recording”The MP4 recorder needs the browser’s WebCodecs VideoEncoder. Where it is missing, the viewer reports This browser has no WebCodecs VideoEncoder — record in Chrome or Edge. Recording the HMI overlay needs tab sharing; without it the viewer says to record in Chrome or Edge or to switch Include HMI off. Cinematic recording writes into a folder you pick, so it needs folder access as well as WebGPU, and the dialog states Requires Chrome or Edge with WebGPU where it cannot run.
Keep simulating in background
Section titled “Keep simulating in background”The simulation clock runs in a dedicated worker, so a hidden or covered tab keeps simulating. Chrome and Edge can freeze a background tab under energy saver. The viewer reports lost simulation time in the Problems panel; add the site to the always-active list in chrome://settings/performance. Background timing in Firefox and Safari has not been measured. An embedded viewer pauses with its tab. See Running in the background.
Connect to CONNECT from a hosted page
Section titled “Connect to CONNECT from a hosted page”A page on https:// that connects to CONNECT on your own machine is a request from the internet to a local address. Chrome and Edge ask once for local network access; allow it. If the status reads CONNECT not reachable or Blocked by the browser:
- Check that CONNECT is running and allow local network access for the site.
- In Safari, and wherever the browser blocks the connection, open the viewer from the CONNECT address instead (for example
http://localhost:5100/), which is same-origin and needs no permission. - A Content Security Policy on a self-hosted page can block
localhost.
Realtime mode
Section titled “Realtime mode”Realtime mode paces the simulation with a 4 ms clock. Measured on Windows 11 with current Chrome and Edge:
- Chrome holds 4 ms in the visible tab, in a background tab and when the window is covered. It does not hold it when the window is minimised.
- Edge holds 4 ms only in the visible foreground tab. In a background tab, when covered or minimised, it drops to steps of about 16 ms.
- On battery, Chromium browsers reach at most about 8 ms.
- Firefox, Safari, macOS and Linux are not tested yet.
The viewer keeps the step rate either way, so a slower clock changes timing precision, not simulated time.
Keep the realvirtual tab visible in the foreground. On HMI or kiosk PCs with Edge, starting the browser with the flag --disable-renderer-backgrounding keeps the clock running when the window is minimised. A clock provided by CONNECT, which removes the browser dependency, is in development.
See also
Section titled “See also”- Browser & GPU setup — choose the right graphics card and fix slow rendering
- Settings — renderer, simulation and background options
- Opening a Twin — where the viewer runs
- realvirtual CONNECT — serving the viewer locally