abox.tools

Language: English
  • English

How to watch a camera from another device

A phone can show a document or another view to your computer without installing a webcam app. Open the camera in one browser, approve a viewer in the other, and keep the source visible while watching.

Open the Remote Camera Open a camera on one device and watch it in another browser, with optional viewer approval. Live video travels directly between them, encrypted.

View as Markdown

What you need

Use two devices with browsers that support camera access and WebRTC. Both need internet access for an introduction and a network that lets them reach each other. A phone on Wi-Fi and a computer on Ethernet can work when that network permits communication between them.

Open this site's trusted HTTPS address. An ordinary HTTP address on a LAN IP cannot request a camera. If your browser or operating system asks for local-network access, allow it for this session.

Start on the camera device

  1. Choose a viewer link name or keep the random suggestion. Leave Require my approval on to approve viewers yourself, or turn it off for automatic viewing. Then choose Start camera. Your browser chooses the initial camera.
  2. Allow camera access. The page requests video only.

Your local preview appears along with a viewer link, your chosen code and a QR code. Nothing is sent as video yet. Keep this page visible and the device awake; switching away stops capture. Stop before changing the link name. Turn off listing before starting if you want to invite viewers by link only. If this browser exposes more than one camera, the Camera selector appears after permission. Choose another camera there to keep the same link and viewer connection; a brief pause may occur on devices that must release the old camera first.

Connect the viewer and approve it

  1. On the other device, open the viewer link or scan its QR code. You can also choose a name under Online cameras, or enter the code in Watch a camera.
  2. Optionally enter a note the source owner will recognise, then choose Connect to camera.
  3. If Require my approval is on, approve the expected request on the camera device. With approval off, the first accepted viewer receives video automatically.

The note is not verified identity. Recognise the person and expected request before approving. Pairing exchanges network addresses even before approval; the source approval setting controls whether an owner action is required before video. With approval off, anyone who knows the link or finds the listed camera can watch while it is free. Changes to the setting apply to new requests; an already connected viewer stays connected. One viewer receives video at a time. If playback pauses, choose Play live video; Full screen enlarges the view where supported.

Stop when finished

Stop camera and end the link releases capture and closes the invitation. Hiding or closing the source page does the same. Disconnect on the viewer clears its live view while the source retains a local preview for another request.

A camera permission granted after Stop is released immediately. Starting again uses the name in the link-name field; choose New random name for a fresh invitation. Ending a session stops future video; a viewer can still keep anything they independently captured on their own screen.

If the devices cannot connect

A shared Wi-Fi name does not establish reachability. Guest isolation, firewalls, blocked local address discovery, browser and OS local-network permissions, or VPN routing can block the direct connection. Stop on both devices, check permissions and the network, then try a fresh link.

Connection details reports the selected candidate types and the viewer's decoded frame count. The tool uses only host candidates, with no STUN server, TURN relay or relay fallback. A VPN, public interface or operating-system route can affect the path; host candidates do not prove that traffic stays inside a physical building.

What the introduction service sees

Opening the page opens a discovery WebSocket to the rendezvous. Start or Connect adds a room WebSocket. The connection stays open during the session, and losing it ends the session. The service sees the code, IP addresses, times, and WebRTC setup descriptions and candidates. Setup messages are visible to that service; live video and the viewer note travel the encrypted peer connection instead.

Discovery lists opted-in camera names grouped by the public IPv4 address or IPv6 /64 seen by the service and this site’s address. This can include strangers behind shared VPNs or carrier networks, and nearby cameras may be missed. Choosing a listed name does not connect. After Connect, the source can require owner approval or accept a viewer automatically. Rooms and listings exist only on open connections. Cloudflare keeps seven-day connection logs containing metadata, never a payload. The usual site advertising scripts can read the page address, including a camera code in its fragment. A code permits a request, so source approval remains essential.

This is a browser camera view: it has no microphone or recording feature, and it does not install a system webcam for other applications.