TIFF to SWF Converter

How to Convert TIFF to SWF Online

1. Upload Your TIFF Files: Drag and drop, or click "+ Add Files" to select one or more TIFF / TIF images. Drop a folder of numbered scans (scan_001.tif, scan_002.tif...) to build a slideshow or animation in order.
2. Pick Merge Strategy and Image Duration: Switch the Merge strategy between "Merge images" (one SWF containing every TIFF as a sequence) and "Video per image" (one SWF per file). Set Duration per frame using presets like 1/24, 1/10, 1/2, 1, 2, 3, 5, or 10 seconds — match 1/24 for cel-style animation, 5 seconds for a kiosk slideshow.
3. Tune Background, Quality, and Resolution (Optional): Set Background Color (Black by default, plus White, Gray, Red, Blue, Green and 20+ named swatches) to fill space when TIFF aspect ratios don't match the output frame. Pick a Quality Preset (Lowest, Low, Medium, High, Very High [Recommended], Highest) or switch to Constant Quality / Constraint Quality for finer control. Choose Keep original resolution or pick a Fixed Resolution preset from 144p up to 4320p (8K), or enter custom Width × Height in pixels or percent.
4. Convert and Download: Click "Convert." Files process on our servers and download as .swf ready for archive uploads, Ruffle playback, or embedding in legacy Flash-aware projects.

Why Convert TIFF to SWF?

TIFF (Tagged Image File Format) is a 1986 raster format originally designed by Aldus and now stewarded by Adobe — popular in publishing, scanning, GIS, and microscopy because it preserves 16-bit channels, alpha, multi-page documents, and lossless LZW or Deflate compression. SWF ("Small Web Format," originally Shockwave Flash) is the vector-and-bitmap container Adobe used for animation and interactive content; the spec was last refreshed in January 2013 at SWF version 19. While Adobe ended Flash Player on December 31, 2020 and blocked browser playback on January 12, 2021, SWF files remain useful for specific niches:

• Flash archive contributions — The Internet Archive's Flashpoint project hosts over 100,000 Flash items and renders them with Ruffle, an open-source (MIT / Apache 2.0) emulator. Bundling stills as SWF lets you contribute matched-format companion content alongside legacy .swf games.
• Ruffle-based slideshows — Ruffle runs as a desktop app, browser extension, or single-line <script> embed; an SWF slideshow built from TIFF scans plays without Flash Player and scales cleanly to the viewer's window via Ruffle's built-in resizer.
• Legacy CD-ROM and kiosk projects — Museums and education vendors still maintain Flash-projector EXE / DMG installs (Adobe's standalone Projector). SWF remains the supported input for these self-contained players.
• eLearning / Articulate / Captivate legacy courses — Older SCORM packages and authoring tool exports expect SWF assets. Converting print-resolution TIFF artwork to SWF keeps those courseware bundles intact during long-tail maintenance.
• Vector / raster hybrid output — SWF can hold raster bitmaps inside its vector container, useful when a downstream Flash-aware tool expects .swf but the source is purely image-based scans or render frames.
• Format-bridging for SWF-only pipelines — Some forensic, archival, or industrial software ingests only SWF. Converting TIFF source frames to SWF gets the imagery into those pipelines without manual re-authoring in Animate.

If you need a modern-browser playback target instead, consider TIFF to MP4 or TIFF to WebM — both play in Chrome, Firefox, Edge, and Safari without an emulator.

TIFF vs SWF — Format Comparison

Quality Preset and Resolution Quick Guide

Frequently Asked Questions

Will the SWF I export still play in 2026 now that Flash Player is dead?

Adobe ended Flash Player on December 31, 2020 and rolled out a content block on January 12, 2021, so modern browsers will not play SWF natively. Your output will play in Ruffle (a Rust-based open-source emulator under MIT / Apache 2.0), Adobe's standalone Flash Projector EXE/DMG, BlueMaxima's Flashpoint, and several archival players. Ruffle supports roughly 99% of ActionScript 1/2 and about 90% of ActionScript 3, but since image-sequence SWFs use no ActionScript at all, they sit firmly in the "fully supported" bucket.

Should I be using SWF at all in 2026, or is MP4 / WebM / GIF a better choice?

For new web or social work, MP4 (H.264) or WebM (VP9 / AV1) is almost always the better answer — both play natively in every modern browser. SWF only makes sense when you're targeting a Flash-specific pipeline: Internet Archive / Flashpoint submissions, Ruffle-powered embeds, older eLearning authoring suites, or legacy kiosk installs. If you're unsure, also try TIFF to MP4 or TIFF to GIF for short loops.

Can I control how long each TIFF stays on screen in the SWF?

Yes. The Image Duration dropdown offers presets from 1/60 second (for 60 fps cel animation) up to 10 seconds per frame (for slow slideshows). Common picks: 1/24 second matches film cadence, 1/10 second mimics classic stop-motion, 1 second is a brisk slideshow, and 3-5 seconds reads as a kiosk loop. Pick once at conversion — there's no per-image timing inside the SWF builder.

What happens with multi-page TIFFs — does each page become a frame?

Multi-page TIFFs (common from scanners and fax software) are flattened into the output sequence in page order, so a 50-page scanned booklet becomes a 50-frame SWF with whatever per-frame duration you chose. If you'd rather keep the scan paginated, TIFF to PDF preserves page boundaries instead.

How does the converter handle TIFFs with different aspect ratios or sizes?

The Background Color option (Black by default) fills letterbox / pillarbox space when a TIFF's aspect ratio doesn't match the chosen output resolution. Combine this with a Fixed Resolution preset (say 1920 × 1080) to force a consistent frame size, or leave Resolution on Keep original if your TIFFs are already uniform. Choose White for print-style scans, Black for photographic stills, or a brand color from the 20+ named swatches.

Will alpha channels and 16-bit color from my TIFF survive the conversion?

Partially. SWF's bitmap layer supports 24-bit RGB plus an 8-bit alpha channel, so transparency is preserved but 16-bit-per-channel color depth gets dithered down to 8-bit. If you need to keep 16-bit fidelity, stay in image space (TIFF to PNG preserves 16-bit channels), or pick a higher-bit-depth video target like ProRes-flavored MOV elsewhere.

Why are file size limits and SWF spec age relevant?

SWF practically caps at 2 GB per file and the spec hasn't been updated since January 2013 (version 19, the last release Adobe published before declaring end-of-life). That means very long slideshows or extremely high resolutions can blow the budget — keep individual SWFs to a few hundred frames at 1080p or below for safe playback in Ruffle and legacy projectors. Split larger jobs into multiple SWFs using the "Video per image" merge mode.

Can I batch-convert hundreds of TIFFs at once?

Yes. Drag the whole folder and pick "Merge images" to build a single sequenced SWF, or pick "Video per image" to get one SWF per TIFF — useful when feeding a per-asset Flash pipeline. There's no artificial file count limit; processing time scales with total pixel volume and your chosen resolution.

Is the conversion lossy, and does SWF compress the TIFFs internally?

SWF stores embedded bitmaps using JPEG (lossy) or zlib (lossless) inside the container. Picking Very High or Highest Quality Preset pushes the encoder toward higher JPEG quality, while Lowest/Low gives more aggressive compression. If your TIFFs are line art, scans of text, or anything with hard edges, lean toward Highest to avoid JPEG ringing; for photographic content, Very High is the sweet spot.