# Remote access from a laptop
The desktop app can serve other devices the same way the Raspberry Pi does.
Phones, tablets and other laptops on the same network then control the gled
running on this laptop, together with its own window.
Open **Config → Remote Access** and tick "Allow browsers and other devices to
control gled". The server starts right away; unticking stops it and
disconnects everyone. The setting is remembered for the next start.
The window shows:
- the ports. HTTPS serves the interface, 8443 by default. The HTTP port only
redirects browsers to HTTPS and can be switched off. A change applies
immediately.
- the addresses to open on the other devices, one per network of this
laptop, each with a button to copy it.
- the fingerprint of the certificate. gled creates its own certificate, so a
browser warns on the first visit. Accept it when the fingerprint matches.
- everyone connected, with their address, gled version and how long they
have been connected.
All connected devices see the same show. A change from any of them reaches the
others within about 30 ms. Keys held on any device count for key inputs, and
they are released when that device disconnects.
Browsers get the full interface, the same as the desktop app, including the
editors and the LED preview. The preview costs each browser showing it about
360 KB/s for a layout of 24 universes. Tool windows open inside the page, and
"Open new window" opens another tab. SVG files are uploaded from and downloaded
to the machine running the browser; the SVG templates are the ones on the
machine running the engine.
## The desktop app as a remote control
The desktop app can also control another gled instead of running its own
engine, for example the Raspberry Pi or a laptop with remote access on:
```sh
gled --connect gled.local:8443 --fingerprint CE:8E:9F:…:7D:3C
```
`--connect` takes the server as you would type it in a browser (`gled.local`,
`gled.local:8443`, `https://gled.local:8443`). `--fingerprint` is the
certificate fingerprint the server shows (in its log, or in the Remote access
window). gled remembers it for that server, so later starts only need
`--connect`. Without a known fingerprint, gled shows the one the server
presented; compare it, then start again with `--fingerprint`. A lost
connection is opened again every two seconds.