prism docs · Getting started · Compatibility and limits
Compatibility and limits
Prepare the browser, computer and connection you will actually use at the venue.
Browser and device checks
| Environment | Release status | What to check yourself |
|---|---|---|
| Windows desktop, Microsoft Edge | Documentation and simulator workflows exercised for this release. | Your GPU, physical outputs, full-screen operation and sustained performance. |
| Chromium in automated tests | Normal CI target for studio end-to-end tests. | Real projector and sound-device routing; CI uses a simulated room. |
| 390 px mobile layout | Documentation layout checked at this viewport size. | This is a layout check, not a physical phone-camera certification. |
| Chrome, Safari, Firefox and phone browsers | Capability-dependent. No additional hardware certification is claimed here. | WebGL2, permissions, camera scanning, codecs, MIDI and screen placement on your actual device. |
Use a desktop computer for editing and projector output. The phone is the scan camera. Camera access requires a secure context: localhost on the host is special, but a phone normally needs trusted HTTPS. Some capabilities, including display selection and system-audio capture, vary by browser. Manual window placement remains available.
Accepted limits
| Item | Limit |
|---|---|
| Outputs | 8 |
| Layers per surface | 4 |
| Mesh grid | Up to 32 × 32 |
| Imported image | 25 MB; stored image scaled to at most 4096 px on its longest side |
| Imported video | 1 GB per file; browser must decode its codec |
| Imported song | 300 MB per file; browser must decode it |
These are acceptance limits, not performance promises. Several large videos, high output resolutions or expensive layered looks can exceed the capacity of an otherwise supported device. Rehearse the busiest scene at show resolution.
What needs a connection?
| Work | Requirement |
|---|---|
| Editing, local media and playback in an already loaded studio | Local assets and browser resources must remain available. Keep the host and output windows open. |
| Opening or reloading the studio | A reachable prism server or development server. An already loaded tab is not an installable offline application. |
| First object-detection use | Internet for the detection-model download. Load it before the venue; later use can reuse its cache, but the cache can be cleared or evicted. |
| Phone pairing and scanning | Phone and host must reach the same server. A local HTTPS server can work on a suitable local network; a public tunnel requires its internet connection. |
| AI generation | Server, configured credentials and internet access to the provider. Previously generated local media can play without another AI request. |
| OSC | A reachable UDP bridge on the server and a connected studio session. |
Prepare before travelling
- Use the final browser, address and profile; import all media and load the detection model if needed.
- Download a checked backup, then test restoring it in a separate profile.
- Rehearse with the final projectors and sound device, including your busiest transition.
- Try the expected venue network conditions. Test a reload as well as uninterrupted playback.
- Disable sleep and disruptive notifications through your computer settings, connect power, and run the pre-show check.
Reviewed for prism 2026.09.29.1 · 29 September 2026. Release notes.