"This video is too large to send."
The common failure case is not professional editing. It is someone trying to share a clip with family, email a meeting recording, or post a game capture where the size limit is the real enemy.
Shrinkr is a dead-simple desktop app for the everyday problem nobody should need a codec manual to solve. Drop in a bloated clip, pick where it needs to fit, and get a smaller MP4 that is ready for WhatsApp, email, Discord, or a cleaner laptop-safe archive.
The UI stays plain-English on purpose. You never see CRF values, codec jargon, or export clutter.
2 videos · 373 MB · sendable on phones without a second thought
Shrinkr was designed around a very specific gap: ffmpeg scares normal people, and classic transcoding tools feel like aircraft dashboards. The app keeps the useful parts of that power, then strips the rest until the workflow is drag, choose, save.
The common failure case is not professional editing. It is someone trying to share a clip with family, email a meeting recording, or post a game capture where the size limit is the real enemy.
WhatsApp, Email, Discord, Optimal, TV, Laptop, and Custom cover the real intent. The interface talks about outcomes, not bitrates.
All encoding happens locally on Windows. Original files stay untouched. The app works offline because a basic utility should not depend on someone else's servers.
The core loop in the PRD is intentionally narrow: load a video, choose what it needs to fit, and save the smaller result. Everything else exists only if it reduces friction around that loop.
Add one file or a short queue. Shrinkr probes the duration, size, and resolution so the app can explain what is being compressed without exposing raw ffmpeg internals.
Choose WhatsApp, Email, Discord, or a quality-oriented preset like Optimal or Laptop. Custom mode adds a plain MB target and a three-stop quality slider.
Encoding progress stays readable with per-file and total progress, cancel support, and a clean completion state that shows exactly how much space was saved.
The shipped desktop UI and engineering PRD point to a product that is broader than "shrink for WhatsApp" but still disciplined enough to remain a utility instead of a media suite.
The technical choices follow the product discipline: Wails for a compact desktop shell, Go for process orchestration, vanilla HTML/CSS/JS for a one-screen interface, and bundled ffmpeg for offline reliability.
The frontend handles state views, queue presentation, and user vocabulary. Go manages probing, ffmpeg execution, progress streaming, and hardware detection. The split keeps the product easy to reason about and avoids stuffing media logic into the UI layer.
The PRD is explicit about constraints: one screen, one primary action, one accent signal, and no hidden technical panels masquerading as helpful flexibility. That restraint is the main product feature.