Drop a cap on that Teams GIF.
Teams accepts gifs up to 10 mb but renders bigger files slowly. Enterprise channels especially throttle. Compress smart, not hard.
- teams caps uploads at 10 mb · enterprise channels throttle larger files · poor compression makes shared work look amateur
gifcap. drop your clip in gifcap. set the cap to 8 mb (under teams's 10). gifcap binary-searches quality until it fits. drag into the teams chat.
| axis | manual ffmpeg / online tools | gifcap |
|---|---|---|
| hits teams's 10 mb cap reliably | trial-and-error | always — binary search |
| quality at 8 mb | often dithered | gifski per-frame palettes |
| workflow | upload-and-wait | drag-drop local |
| corporate firewall | may block external uploaders | processes locally |
| cost | free | free tier; pro $29 lifetime |
How gifcap solves this — in detail
Teams is the canonical "upload, fail silently" platform. The 10 MB attachment cap is documented but enterprise tenants often have stricter limits applied by IT, and corporate proxy software sometimes intercepts uploads to online compressors entirely. The local-encode workflow sidesteps both problems.
gifcap binary-searches quality to fit under 8 MB (with 2 MB safety margin under any tightened tenant cap), and gifski's per-frame palette keeps the GIF readable on Teams' often-aggressive image compression. The output ships on first try, autoplays inline in chat and channels, and renders on the Teams desktop client, web client, and mobile app identically.
The corporate-firewall pattern is the underrated win here. gifcap makes only one outbound network call — the optional update check to gifcap.io/version.json — which most enterprise proxies allow. Your bug repros, demo recordings, and internal walkthroughs never traverse the corporate boundary.
Microsoft Teams — current GIF limits
- Per-attachment cap: 10 MB
- Total chat attachment cap: 250 MB
- Autoplay threshold: ~10 MB (above this, click-to-play)
- Mobile clients: autoplay supported on iOS / Android
- Enterprise tenant overrides: IT can lower per-attachment cap
- Giphy integration: separate, picker-based; doesn't apply to file uploads
- Recommended encode: 8 MB target with safety margin