Manvith Kotian

@kwill_2026 Thanks, Kanav! Squish keeps the video on your device, but it loads the file into the browser’s memory rather than streaming it from disk. The input limit is 2 GB, and a recording near that size may still run out of memory during compression. For a large screen recording, I’d split it into shorter clips first or use a desktop compressor.

@waqasjawed24 Thanks, Waqas! I wanted to make those common sharing limits easier to deal with while keeping the video on your device. Glad you found the presets practical!

@zawyan1122337 Thanks, Zawyan! Keeping the video on your device was the main goal, and I’m glad the WhatsApp and Discord presets stood out. Appreciate the support!

@peterjduffy Thanks, Peter! Squish loads the video into FFmpeg’s browser memory for processing; it doesn’t stream from disk. There’s a 2 GB input limit, and an hour of 4K is well beyond the recommended range—it could run out of memory even below that limit. For a recording that large, I’d split it into shorter files before using Squish.

@eliasmillercom Thank you

@tiktokforu4 Thank you! Keeping videos on your own device was a big reason I built Squish. Glad the WhatsApp presets stood out - they’re there to make sharing a little less fiddly!

@killer3p0 Thanks, James! Browser memory is the main constraint. Longer 1080p clips can run out of memory, especially on phones, so I wouldn’t guarantee them across all devices. Squish is best suited to shorter clips; for larger videos, a desktop browser, trimming first, or choosing 720p/480p can help reduce the load.

@moroctrip Thanks, Kha! Really appreciate the support and good wishes 🙌

@anubhavpurohitno5 Thank you, Anubhav! I wanted the page to make it easy to understand Squish and get straight to compressing. Glad you liked it!

@wesleyworks Thanks, Wesley! Shrinking a screen recording for Discord or trimming a phone video for WhatsApp are two workflows Squish is built for. Good point about showing those examples and comparing the trade-offs with other tools - that would make the page more useful.

@zeq29654 Thanks so much! Glad you like Squish 😊 Would love to hear how it works for your videos!

@elia8o Thanks for the thoughtful questions, Elia! Squish relies on FFmpeg’s automatic rotation handling and keeps audio enabled by default. The iPhone preset outputs MP4 with H.264 video and AAC audio. I’d want to validate more real iPhone HEVC samples before promising rotation and audio/video sync across all recordings. A compatibility note explaining those limitations and which preset to choose would be useful - thanks for suggesting it!

@rahulagrawalrahulagrawal Thanks, Rahul! That was exactly the idea - keep videos on your device and make getting them ready to share easier. Glad the presets and file-size targeting stood out to you!

@prolifik Glad this is something you needed, Aurimas! 🙌 Hope it saves you some time the next time a video is too large to share.

@mrcompengphz Thanks, Michael! Would love to hear how it works for your videos. Let me know if anything feels confusing or doesn’t work as expected.

@abhijith Thank you

@zenanythin Appreciate the detailed feedback, Zen! To answer your first question - right now it calculates and displays a Likely Output size range preview before encoding, but it doesn't auto-estimate the exact resolution or quality trade-off drop beforehand when hitting a strict target file size. That’s a really smart feature idea to explore!

And your second point regarding a clear notice that closing the tab cancels the job is spot on - definitely a crucial UX safety check for larger files. Thanks for calling that out!

@payamprivate Thanks a lot, Peyman! Spot on regarding the local-first WASM architecture, keeping it zero-overhead while guaranteeing total privacy was the core goal. Really appreciate the support!

@hashtagasad00 Appreciate the kind words! Let me know if you run into any heavy files or edge cases testing it out.

@sudipgautam Thank you