Initializing... drag & drop files here
Supports: TIFF, TIF
.tif or .tiff images from your computer. Upload one image for a single-frame Flash video, or hundreds of numbered scan / microscope / satellite frames (frame_0001.tif, frame_0002.tif…) to assemble a sequence. Batch is supported — drop in a whole folder..flv — no sign-up, no watermark, no installation of an obsolete Flash plug-in required.TIFF (Tagged Image File Format) is a lossless still-image container favored by scanners, microscopes, satellite imaging, GIS, and pre-press workflows; FLV (Flash Video) is Adobe's legacy streaming-video container, first released September 2003 and discontinued for browser playback when Adobe ended Flash Player support on December 31, 2020. Despite that EOL, FLV files still appear in archives, e-learning platforms, surveillance systems, RTMP ingest pipelines, and legacy CMS uploads — and converting a TIFF sequence to FLV is the way to deliver imagery to any of them. Common reasons:
.flv. Wrap a TIFF scan or diagram in a 10-second FLV to satisfy the upload validator without rebuilding the course module..swf shells that load .flv clips. A still TIFF logo or product photo converted to FLV plays inside the kiosk without changing the parent project file.If your audience is modern, prefer TIFF to MP4 or TIFF to WebM — both play natively in every current browser. Use FLV only when the destination platform genuinely requires it.
| Property | TIFF | FLV |
|---|---|---|
| Media type | Still image (can hold multi-page TIFF) | Video container |
| Released | 1986 (Aldus, now Adobe) | September 2003 (Macromedia, then Adobe) |
| Typical codec | Uncompressed, LZW, ZIP, JPEG, or Deflate | FLV1 (Sorenson Spark / H.263), VP6, H.264, Screen Video |
| Audio support | No | Yes — MP3, AAC, Nellymoser, Speex, ADPCM, PCM |
| Frame count | 1 (single) or multi-page | Many (1 → millions) |
| Browser playback (2026) | Not natively — image viewers / Photoshop / IrfanView | None natively; VLC, ffmpeg, MPV, legacy Flash projectors |
| Color depth | Up to 16 bits/channel, plus alpha | 8 bits/channel YUV 4:2:0 (typical) |
| Status | Current, widely used in pre-press / scientific | Deprecated since Flash EOL (Dec 31, 2020) |
| FLV codec | Released | Best for | Notes |
|---|---|---|---|
| FLV1 (Sorenson Spark) | 2003 | Maximum legacy player compatibility | H.263 variant; the original FLV codec — every FLV decoder ever shipped supports it |
| VP6 | 2003-2005 | Mid-era YouTube / web video archives | On2 codec; better quality than FLV1 at the same bitrate, but heavier to decode |
| H.264 | added 2007 (Flash Player 9.0.115+) | Modern playback inside an FLV wrapper | Same codec as MP4 — best quality, but requires a player that handles H.264-in-FLV |
| Flash Screen Video (FLASHSV / FLASHSV2) | 2004 / 2008 | Screencast and slide-deck capture | Lossless screen-share codec; large files, but pixel-accurate for text and UI |
No. Chrome, Firefox, Edge, and Safari all removed Flash Player at the end of 2020. FLV in 2026 plays in standalone video players (VLC, MPV, MPC-HC), in FFmpeg-based pipelines, and inside legacy desktop applications that bundle their own decoder — but not in any current browser without a third-party extension. If browser playback matters, convert your TIFFs to MP4 instead.
Three real reasons keep FLV alive: (1) archival — petabytes of FLV exist in older content libraries, broadcast tape transfers, and Wayback-archived sites; (2) legacy infrastructure — DVR firmware, LMS uploaders, and RTMP ingest endpoints that were never updated; (3) tooling lock-in — corporate SOPs and government systems that hard-code .flv as the accepted upload extension. Converting TIFF to FLV is almost always a compatibility-with-old-system task, not a quality choice.
Pick FLV1 if you need the widest possible legacy reach — every FLV decoder since 2003 reads it. Pick H.264 if your target player is FFmpeg-based (VLC, ffplay, MPV) or Flash Player 9.0.115 or later — you get a much sharper image at the same bitrate. Avoid the Flash Screen Video codecs unless you're specifically capturing UI screenshots or text-heavy slides, where their lossless mode shines.
FLV (released 2003) uses a custom container with 9-byte header and 15-byte FLV tags. F4V (released December 2007) uses the ISO base media file format — essentially MP4 with a different extension — and supports only modern codecs (H.264, AAC) while dropping legacy codecs like Sorenson Spark and VP6. If you have flexibility, F4V is the better target inside the Flash ecosystem; FLV is for true legacy compatibility.
Output duration = number of TIFFs × Image Duration. 30 microscope frames at 1 second each = 30-second FLV. 240 satellite TIFFs at 1/24 s (cinematic frame rate) = 10 seconds. The Image Duration setting is per-image and applied uniformly to every TIFF in the upload set.
Multi-page TIFFs are unwrapped during processing — each page becomes one frame in the output FLV, in the page order stored in the TIFF directory. A 50-page scanned document TIFF at 2 s per frame produces a 100-second FLV slideshow. If you need to split a multi-page TIFF first to inspect or reorder pages, see TIFF to JPG and then upload the JPGs in your preferred order.
No — FLV doesn't natively support an alpha channel in its standard codecs (FLV1, VP6, H.264 all encode YUV 4:2:0 without alpha). The Background Color setting fills letterbox / pillarbox padding with a solid color (black is standard; pick from 24 named colors). For animations that need transparency, use TIFF to GIF or convert to WebM with the VP9 alpha-channel option.
TIFF decoding (especially LZW, ZIP, JPEG-in-TIFF, and 16-bit-per-channel variants) plus FLV muxing requires a heavier FFmpeg pipeline than the browser can sandbox quickly for large image sets. The upload runs over HTTPS, files are processed in an isolated worker, and outputs are deleted from xconvert's edge servers automatically after the download window closes — no account, no watermark, no manual cleanup required.
Free anonymous use handles individual TIFFs up to roughly 500 MB and batch jobs into the multi-gigabyte range; a registered account raises both limits. For massive image sequences (thousands of high-resolution scans), the practical bottleneck is upload bandwidth rather than the converter — split the job into chunks of 200-500 TIFFs at a time if your network is slow.