How to share your screen in WolfStorm

WolfStorm can put your actual computer screen — a browser tab, a single window, or a whole monitor — live onto the face of a prim in world, with sound. No plugin, no OBS, no stream key, no media server to rent. Here is how to do it, start to finish.

What you need

• WolfStorm in a desktop browser. Chrome, Edge or Brave are best, because they can capture audio along with the picture. Firefox shares happily but gives you video only. iPhone and iPad cannot capture a screen at all, so on those the Screen button simply is not there rather than being there and failing.
• A prim you can edit. Your own build, or something you have edit rights on. Turning a face into a media face goes through the same permission check as any other edit, so a stranger's prim will not take your share.
• To be logged in. The share is minted against your live session, so it is your avatar doing the sharing.

Step by step

1. Rez your screen. A plain box, stretched flat, is all it needs to be. Make the face roughly the shape of what you are about to share — a 16:9 face for a monitor or a video — otherwise the picture gets stretched or letterboxed to fit.
2. Open Build from the menu bar at the top, and choose the Edit tool.
3. Switch to Select Face and click the face you want the picture on. This matters: the share goes onto one face of one prim, not the whole object. On a linkset, click the face on the actual child prim — whatever you clicked is exactly what lights up.
4. Click Screen on the toolbar along the bottom.
5. Pick your source in the browser's own picker. Entire screen, a window, or a tab — and tick the box to include audio if you are sharing something with sound. WolfStorm cannot pre-select any of this for you: that picker is the permission, and it is your browser asking, not us.
6. That is it. The face goes live immediately — you see your own screen on it straight away, not a delayed copy round-tripped through a server. The toolbar button relabels to Stop, and hovering it tells you how many people are watching.

Stopping

Click Stop on the toolbar, or use your browser's own “Stop sharing” bar — either one ends it properly. WolfStorm clears the prim face, puts back whatever texture was on it before, and kills the link. It does not leave a dead media face behind or leave your browser thinking it is still sharing.

Who can see it

Everyone in the region who can see that prim. Other WolfStorm users get the video straight onto the face over WebRTC. Firestorm and other desktop viewers with media enabled get it too, through a small page on the face — audio plays by itself inside Firestorm's built-in browser, and viewers get the usual in-world media bar to stop or mute it if they want to.

One current limit worth knowing: your browser encodes a separate stream for every watcher, so a share tops out at seven viewers at once, and the eighth is turned away with a message. That is the honest state of it today. A proper media server removes the cap and is the next piece of work; nothing you do here changes when it lands.

Quality, and why it is capped

Shares run at up to 1280×720, 30 frames a second, 2 Mbps. That is a deliberate ceiling, not a limitation of the browser. Because every watcher costs you another encoded stream, a 1080p60 share fully fanned out would need something like 35 Mbps of upload — which almost nobody has. 720p is comfortably legible for slides, a terminal, a web page or a video, and 2 Mbps stays inside an ordinary home connection even with a full audience. When the media server lands, 1080p becomes affordable and the cap goes up.

Privacy — read this bit

The address of your share is broadcast to the whole region. That is not a leak, it is simply how media on a prim works: every viewer in the region has to be told where to look, or nobody would see anything. So treat a screen share as public to that region. Anybody who can see the prim can watch it.

What that address does not give away: it is tied to that one share and nothing else. It cannot be used to join voice, it does not carry your identity, and it expires after four hours. The moment you press Stop it is revoked — anyone reopening it just gets told the share has ended.

The ordinary sense rule applies, as it would anywhere: share a tab or a single window rather than your whole desktop, and close your mail client first.

If something does not work

• No Screen button at all. Your browser cannot capture a screen — that is iOS, or a page not served over HTTPS. Nothing to configure; use a desktop browser.
• “Select the prim you want to share onto first.” Nothing is selected. Build → Select, then click the prim.
• “Choose the face to share onto.” You have the prim but not a face. In Build, switch to Select Face and click the face.
• “This region does not offer the ObjectMedia capability.” That region cannot do media on a prim, so no viewer could show the share. Try another region.
• “No session token — log in again.” Your session has aged out. Reload and log in.
• “Already sharing.” One share at a time per viewer. Stop the current one first.
• You clicked Screen, dismissed the picker, and nothing happened. That is correct behaviour — cancelling the picker is not an error and does not deserve a red banner.
• The picture freezes. Do not minimise the window or tab you are sharing. A minimised source can stop producing frames, and that is the browser's decision, not the viewer's.

What it is good for

Slides at a class without uploading them as textures one at a time. A terminal or an IDE during a build session. A film night where the film is whatever is in your browser tab. A shared design doc that everyone standing around the prim can read. It is the same thing you would do on a video call, except the screen is a physical object in a place people walked to.

WolfStorm runs in a browser tab with nothing to install — open it here and try it.