Link budget optional
Set what you are transmitting over. Everything downstream can aim at this number.
Off. Kompressed still crops and squeezes exactly the same — you just aim at a file size, or drive quality by hand, and nothing talks about airtime.
Load something
Nothing leaves this machine. All the encoding happens in the browser.
Drop a photo, video or recording — or several photos at once for a batch
JPEG, PNG, HEIC, MP4, MOV, WebM, WAV, MP3, M4A, AIFF — iPhone photos and voice memos included
Crop and forge
Still image
Output
Dekompressor
Receive-side repair. It undoes what a low bitrate did — it does not invent detail, and nothing here is a model.
Batch stills
Video
Voice
Target
Result
Text armor for a keyboard link, packets for a one-way link with no retries, a QR for a phone-to-phone handoff, an ATAK package for the map.
Log
Session record
What has been squeezed and sent from this machine. Survives a reload, because the question you get asked afterwards is what went out and how big it was.
What actually moves the needle
- Frame rate, then resolution, then bitrate. Going 30 fps to 3 fps is a 10× cut before the encoder does anything clever. For a static scene — a map, a damaged bridge, a whiteboard — nobody misses the frames.
- Trim ruthlessly. Six seconds of the thing you care about beats forty seconds with it in the middle. Duration multiplies straight into bytes.
- Crop before you scale. Cropping throws away pixels the encoder would otherwise spend bits on. Scaling a wide shot down just makes everything equally unreadable.
- Grayscale when colour is not the message. Chroma is roughly a fifth of the bits and is often decoration.
- Send a still if a still will do. An AVIF at 4 KB carries more usable information than four seconds of 12 kbps video, and it arrives in one block.
- Long keyframe intervals shrink files and raise the stakes. A corrupt keyframe ruins everything until the next one. Over a lossy link, shorter GOPs cost bytes and buy you recovery.