Commons’ own File types page allows exactly three video formats — .webm, .ogv and .mpg/.mpeg — and excludes MP4 and MOV because H.264 and H.265 “could require royalty payments”. The plain upload form stops at 100MB, 5 GiB is reachable only through UploadWizard’s chunked upload, and Chrome removed Theora decoding in version 123, leaving WebM as the only accepted format that still plays. Here are the sourced rules, a WebM conversion that runs entirely in your own browser, and an honest account of when Commons’ own VP9 + Opus guide is the better route.
Google’s own help page pins a Business Profile video with three numbers — up to 30 seconds, up to 75MB, 720p or higher — and gives profile photos their own 10KB–5MB JPG/PNG window. Customers posting to your place on Maps get the same 30-second ceiling. Here are the sourced rules, why the lossless cut should aim a few seconds short of that ceiling, and how the business photos can come out of the same walkthrough as exact frames — all on your own device.
Apple’s own spec sheet bounds an app preview hard: 15 to 30 seconds, .mov/.m4v/.mp4, H.264 or ProRes 422 (HQ), at most 30fps and 500MB, at exact per-device resolutions. Google Play takes no file at all — a public-or-unlisted, ad-free YouTube URL that autoplays only its first 30 seconds. Here are the sourced rules, why a screen capture of an app is the footage re-encoding hurts most, and the keyframe detail that can push a lossless cut past Apple’s hard ceiling.
Zoom’s free plan records locally to an MP4 on your own desktop, per Zoom’s own pages — its cloud trimmer is paid, destructive, and capped at 5 trims per 12 hours. Teams saves an MP4 to the organizer’s OneDrive that Microsoft sizes at 400MB per hour and expires after 120 days by default. Meet records only on paid Workspace editions. Here are the sourced facts, and how a lossless on-device trim turns an hour of internal discussion into the one clip someone actually needs — without the recording ever leaving your machine.
Etsy caps a listing video at 15 seconds and strips its audio, per its own help center — while allowing a roomy 100MB. eBay wants one minute or less, specifically in H.264, and reviews every upload. Shopify hosts 10 minutes and 1GB, and even accepts WebM. Here are the sourced numbers, the one case where file size still bites (4K/60 at about 400MB per minute), and why a lossless trim on your own device is the move that fits all three.
Notion’s Free plan caps every uploaded file at 5MB per its own help center — and its supported-format list names MP4, not WebM, for video. Trello’s free boards allow 10MB per attachment per Atlassian’s docs, and Asana allows 100MB per file on every plan. Here are the sourced numbers, roughly how many seconds fit in each budget at NearVid’s real presets, and the sub-300px GIF trick that animates a demo right on a Trello card cover.
WhatsApp’s normal media path re-encodes video to 480p — 720p with the HD option, and still compressed even then, per 9to5Mac’s report on the setting. Attaching the same file as a document skips compression entirely and allows up to 2GB, per WhatsApp’s own announcement. Here’s what each path really does, the codec catch of a document send, and how NearVid’s lossless trim makes the full-quality path practical.
On August 13, 2026, Discord raised the free upload cap from 10MB to 20MB — still below the old 25MB, with Nitro tiers unchanged at 50MB and 500MB. Here are the sourced numbers, roughly how many seconds of WebM or MP4 fit in 20MB at NearVid’s real quality presets, and the lossless trim-first workflow that gets a game clip under the cap on your own device.
LinkedIn’s own Help Center caps native video at 5GB and 15 minutes — but plenty of videos that fit both limits still get stuck at 0%, because the codec inside a supported .mov or .mp4 container, not the container itself, is what actually breaks. Here are LinkedIn’s real upload specs, the HEVC trap iPhone and Mac footage falls into, and how NearVid’s Trim and Convert to WebM/MP4 fix it locally before you upload.
Apple Podcasts launched real video support in early 2026 and Spotify is adopting the same tech, with Edison Research finding weekly listeners now nearly as likely to watch as to listen. None of that changes what Apple’s own RSS spec accepts — MP3 or AAC, not video. Here’s why a video-recorded episode still needs its audio pulled out separately, and how NearVid’s Extract Audio does it locally, on any browser.
X’s free tier caps video at 140 seconds and 512MB, per its own Help Center — Premium raises that to 4 hours and 16GB. Bluesky’s own protocol source accepts MP4 only and its app enforces a real-world cap around 100MB, with a 3-minute length ceiling since March 2025. Here are the current, sourced numbers for both, and how NearVid’s lossless trim gets one clip ready for whichever cap is tighter.
iPhones have recorded video as HEVC by default since iOS 11, and Windows still doesn’t include an HEVC decoder — Microsoft’s own support page shows the exact “you need an extension” error and its $0.99 one-time fix, repeated on every PC. Here’s why it happens, and how NearVid converts the file locally, no purchase or upload required.
In March 2026 YouTube raised its desktop custom-thumbnail upload limit 25x, from 2MB to 50MB, for sharper thumbnails on TV — but mobile app uploads and the Data API’s thumbnails.set endpoint are still capped at 2MB. Here’s YouTube’s own spec, what changed, and how NearVid’s native-resolution frame extraction fits into uploading one.
Slack’s own help center caps a custom emoji GIF at under 128KB and 50 frames. Here’s why a straightforward export usually blows past both, and how to use NearVid’s trim, fps, and width controls — in the right order — to land under the limit without repeated failed uploads.
Free browser-based screen recorders default to WebM because that’s what the browser’s own MediaRecorder API supports best — but caniuse.com puts full WebM playback on iPhone Safari at iOS 17.4+ only, and Microsoft’s own PowerPoint docs list WebM for Windows alone, needing a separate codec install just for audio. Here’s exactly where it breaks, and how NearVid’s Convert to MP4 fixes it locally.
Gmail, Outlook.com, and Yahoo Mail all cap an email attachment at 25MB. Here are the current, sourced limits, why the real safe target is a bit under that line, and how NearVid’s new “≈” expected-output-size estimate next to the Quality select tells you whether a preset will fit before you sit through a re-encode.
OpenAI’s transcription API caps every upload at 25MB, Gemini Apps’ free tier allows double the duration for audio versus video, and Otter’s own troubleshooting advice is to strip the video anyway. Here are the current, sourced limits, and why pulling just the audio track first — NearVid’s extractAudio() — routinely buys back most of that budget.
web.dev’s own example: the same clip runs 3.7MB as a GIF, 551KB as MP4, and 341KB as WebM. Here’s what the Lighthouse “use video formats for animated content” audit actually checks, the markup that makes a video behave like a GIF, and how far a tool like NearVid does (and doesn’t) get you from a source clip to a page-ready file.
GitHub caps images and GIFs at 10MB no matter your plan, Discord’s free tier dropped to 10MB in 2024, and Slack allows up to 1GB but only keeps free-plan history for 90 days. Here are the current, sourced limits, why GIF blows past a video’s budget for the same footage, and why trimming your clip down before converting is the biggest lever for staying under any of them.
Instagram Reels and YouTube Shorts cap out at 3 minutes, TikTok uploads at 10 — and all three keep raising the ceiling. Here are the current, sourced numbers, why NearVid’s lossless trim beats re-encoding before you post, and the specific, cited reason (a 2025 FBI warning and a 2024 data leak) to trim on your own device instead of another upload-based converter.
NearVid’s frame-extraction tool grabs an exact frame, not just the nearest keyframe — but the wrong second still gets you motion blur or a half-formed transition. Here’s how the seek actually works, what makes a still look bad, and how to pick a timestamp with no live preview to check it against.
The official @ffmpeg/core-mt package turned out to be a GPL build, not LGPL. Here’s how we found out, why hiding the encoder in the UI doesn’t fix a compile-time license problem, the self-built replacement, and the real linker bug we hit shipping it.
A WebCodecs spike found H.264 completely unavailable in its own test browser, yet proved the demux-decode-encode-mux-play pipeline for real with VP9+Opus. Here is the two-stage story: what the spike proved and could not prove, two real bugs it hit, and why production shipped Mediabunny instead of the spike’s mp4box.js + mp4-muxer.