v1.0 · Rust + Web

The sweet spot between
SSH and VNC

Remote desktop control for when you're on a tight data budget. No stream, no waste — just on-demand screenshots with tap, type, and crop from your phone.

~100B
Per tap command
~50-200KB
Per screenshot
Few MB
Monthly usage

On a data budget?

Only one of these respects your cap.

No GUI

SSH

Terminal-only. Great for servers, useless when you need to see what you're doing.

No desktop
Data hog

VNC

Full desktop, but streams the framebuffer nonstop. A few sessions blow through 100 MB.

3-5 GB/mo
Sweet spot

SnapRemote

Desktop control on demand. Screenshots only when you ask — tap, type, crop, done.

~5 MB/mo
~100 B
per tap command
~100 KB
per screenshot
2,500×
less data than VNC

Three moves, full control

Your phone becomes a remote desktop — no app install, no stream, no cloud.

Open the link

Run SnapRemote on your desktop, open the printed URL on your phone. That's it — no app, no account, no install on the phone side.

Tap the screen

Tap where you want to click. Short tap = left click, long press = right click. The screenshot updates instantly.

Crop & type

Pinch-zoom, crop a region to save data, and type text from your phone keyboard. Only what you need, nothing more.

Everything you need, nothing you don't

Purpose-built for remote desktop access when every kilobyte counts.

On-demand screenshots

No video stream, no session recording. Every capture is a single WebP image — instant, on request, zero waste.

Type from your phone

Full keyboard input sent from your phone to the desktop. Perfect for typing passwords, URLs, or commands remotely.

Region cropping

Draw a rectangle on screen to capture only what matters. Smaller payloads, faster response, less data used.

Works over any network

Runs on a local HTTP server. Pair with Tailscale, ngrok, or SSH tunneling for remote access from anywhere.

Adjustable quality

Fine-tune screenshot resolution and WebP quality to match your connection. From 480p at 5% to source at 100%.

Auto-refresh timer

Set an interval for periodic screenshots. Useful for monitoring long-running processes without manual refreshing.

See the difference

Real-world data usage comparison for remote desktop tasks.

One month of light remote desktop use

Based on ~50 interactions, typing, and screenshots

VNC
~3-5 GB
continuous framebuffer stream
SnapRemote
~2-8 MB
on-demand, only when you act
That's up to 2,500× less data than VNC for the same tasks.

Get SnapRemote

Cross-platform, zero dependencies. One binary, no setup.

View on GitHub →

Common questions

Everything you're wondering about SnapRemote.

Is this VNC?
No. VNC continuously streams the framebuffer. SnapRemote only captures when you ask for it. Think of it as on-demand screenshots with remote input, not a remote desktop session. This is why SnapRemote uses a fraction of the data.
Do I need to install anything on my phone?
No. Your phone just needs a modern browser. SnapRemote's web UI works in Chrome, Safari, and Firefox. The server runs on your desktop — your phone connects to it over HTTP.
Can I access my desktop from anywhere?
SnapRemote runs a local HTTP server. For remote access, pair it with Tailscale, ngrok, or an SSH tunnel. Your desktop doesn't need a public IP — just a network path from your phone.
What are the system requirements?
Linux: grim (Wayland) or ffmpeg (X11). Windows: Nothing — just run the .exe. The server is written in Rust and uses zero dependencies beyond the capture backend.
Is there audio or video streaming?
No. SnapRemote is strictly screenshots and input. No audio, no video stream, no session recording, no cloud. Everything stays on your network.
Can I use it over a metered connection?
Absolutely — it's designed for it. A screenshot is 50-200 KB. A click is ~100 bytes. You could use SnapRemote daily on a 100 MB data cap without breaking a sweat.