Initializing... drag & drop files here
Supports: TS
A .ts file is an MPEG Transport Stream container, originally specified in ISO/IEC 13818-1 for broadcast TV, ATSC, DVB, and IPTV delivery. You end up with TS files when you record from a digital tuner, capture a stream with VLC or ffmpeg, rip HDV camcorder footage, or export segments from a security DVR. GIF strips that out to a single looping clip that plays inline anywhere an image does — no codec, no autoplay-with-sound prompt, no embed widget.
| Property | TS (MPEG Transport Stream) | GIF |
|---|---|---|
| Primary use | Broadcast TV, IPTV, DVR capture | Animated images, web/chat loops |
| Standard | ISO/IEC 13818-1 (MPEG-2 Systems) | CompuServe GIF87a / GIF89a |
| Video codec | H.264, H.265, MPEG-2 video | None — palette-indexed frames |
| Audio | AAC, AC-3, MP2 | None |
| Color depth | Up to 10-bit per channel (HDR-capable) | Up to 256 colors per frame |
| Compression | Inter-frame (B/P frames) | Per-frame LZW |
| Looping | Player-controlled | Built into format (NETSCAPE2.0 ext) |
| Browser support | Limited — needs MSE/HLS or download | Native everywhere since 1990s |
| Typical use | A 30-min DVR record at 8 Mbps ~= 1.8 GB | A 4-sec 480p loop ~= 1-4 MB |
| Setting | Smooth motion | Small file | Good for |
|---|---|---|---|
| 24 FPS, 256 colors | Excellent | Largest | Game clips, sports highlights |
| 15 FPS, 128 colors | Smooth | Medium | Screen recordings, tutorials |
| 10 FPS, 64 colors | Acceptable | Small | Reddit/Discord reaction loops |
| 8 FPS, 32 colors | Choppy | Smallest | Flat graphics, slideshow loops |
GIF has no inter-frame compression — every frame is stored as a palette-indexed bitmap. The TS uses H.264 or MPEG-2 inter-frame compression, which encodes only the changes between frames. For motion-heavy content (sports, gameplay), the same 5-second clip can balloon from a 2 MB TS to a 15 MB GIF unless you cap framerate (8-12 FPS), palette (64-128 colors), and resolution (360-480p).
The format itself has no hard duration cap, but every frame counts. A 1080p clip at 30 FPS hits roughly 1.5-3 MB per second after palette reduction, so most usable shares stay under 6 seconds. For longer content, downscale to 480p, drop framerate to 10-15 FPS, and trim aggressively — or keep it as MP4/WebM.
No. GIF has no audio track in the specification. If you need the audio, extract it separately (TS streams typically carry AAC or AC-3) using a TS to MP3 or TS to WAV conversion, or convert to a video format that keeps both tracks like TS to MP4.
Possibly. Broadcast TS streams (1080i, 480i) are often interlaced, and GIF stores progressive frames. If you see horizontal comb lines on motion, the source is interlaced; a video filter pass like ffmpeg's yadif deinterlaces before the GIF encode. Most browser-side converters apply a default deinterlace for SD/HDV sources, so 1080i HDV camcorder footage usually comes out clean.
Depends on the content. Photographic or live-action footage benefits from the full 256 colors plus dithering — skin tones and gradients look terrible at 32 or 64. Flat graphics, screen recordings, and animation often look fine at 64 or even 32 colors and shrink to half the size. Try 128 first; it's the sweet spot for most TS captures.
This converter currently turns the whole TS into a GIF — for trimming first, use Video Cutter to slice the TS to your target window, then run that shorter file through this tool. Most usable GIFs are 1-5 seconds anyway, so trimming the source is almost always the right move.
Yes. The converter writes the NETSCAPE2.0 application extension with a loop count of zero (infinite), which is what browsers, Discord, Reddit, and chat clients use to autoloop. If you want a single-play GIF, that's a niche workflow most viewers don't support cleanly anyway.
Yes. Conversion runs on our servers and works in current Chrome, Firefox, Edge, and Safari (desktop and iOS). Large TS files (multi-GB DVR captures) hit memory ceilings faster on mobile — for anything over 500 MB, a desktop browser is more reliable.
No hard cap for casual use, but giant TS files (multi-hour DVR captures over 4-5 GB) can stall in lower-RAM browsers. For long recordings, trim first or downscale resolution before converting. Batch jobs of many smaller TS clips run fine.