Initializing... drag & drop files here
Supports: X3F
X3F is Sigma's proprietary RAW container written by Foveon X3-sensor cameras: the SD9 (2002), SD10, SD14, SD15, SD1/SD1 Merrill, DP1/DP2 (and Merrill variants), the dp Quattro line from 2014, and the sd Quattro / sd Quattro H from 2016. SWF (Small Web Format / Shockwave Flash) is the legacy Adobe playback container that Adobe formally end-of-lifed on December 31, 2020, with Flash Player blocking embedded content starting January 12, 2021. Almost no modern browser will play a fresh SWF, so this conversion is overwhelmingly an archive or pipeline task rather than a publishing one.
| Property | X3F (Sigma Foveon RAW) | SWF (Shockwave Flash) |
|---|---|---|
| Type | Still-image RAW container | Vector/bitmap animation + ActionScript runtime |
| First released | 2002 (Sigma SD9) | 1996 (FutureWave / Macromedia, then Adobe) |
| Vendor / spec owner | Sigma Corporation (proprietary, partially reverse-engineered) | Adobe (open spec, but runtime end-of-lifed) |
| Magic / signature | ASCII "FOVb" header | ASCII "FWS" (uncompressed) / "CWS" (zlib) / "ZWS" (LZMA) |
| Typical file size | 45-50 MB per frame (Merrill 46 MP, Quattro 39 MP equivalent) | Varies — a 1080p 30-second slideshow is typically 2-30 MB |
| Color model | Three stacked photodiodes per pixel (blue ~0.2 μm, green ~0.8 μm, red ~3.2 μm depth) | 32-bit RGBA bitmap frames or vector shapes |
| Native software | Sigma Photo Pro (free download from Sigma) | Adobe Flash Player (EOL Dec 31, 2020); Adobe Animate still exports SWF |
| Browser playback in 2026 | None | None natively; only via Ruffle emulator |
| Best use today | Archival photographic master | Legacy SWF-only toolchains, retro web archives |
| Preset | Approx CRF range | Best for |
|---|---|---|
| Lowest | Very small file, heavy blockiness | Thumbnail previews, transcript-style storyboards |
| Low | Small file with visible compression | Internal proofing, draft kiosk loops |
| Medium | Balanced size and detail | Default for general slideshow output |
| High | Subtle artifacts on fine detail | Print-derived slideshows where some softness is acceptable |
| Very High (Recommended) | Near-transparent compression | Foveon-quality archive output for SWF projectors |
| Highest | Largest file, minimal compression | Master archive copy when storage is not a constraint |
Almost no one is publishing SWF to the open web today — Adobe ended Flash Player support on December 31, 2020 and began blocking content January 12, 2021, and every mainstream browser has removed the runtime. The realistic use cases left are archival: feeding a museum kiosk that still uses Adobe Flash Player Projector, regenerating an asset for an older Articulate or Adobe Captivate project, producing SWF for the Ruffle open-source emulator, or migrating a Foveon photography pipeline that historically dumped slideshow SWFs. If you actually want to share Foveon images as video on the modern web, use X3F to MP4 or X3F to WebM instead.
Probably not in a stock browser. Chrome, Firefox, Edge, and Safari all dropped Flash Player support in 2020-2021, and Safari 14 (September 2020) was the first macOS release shipped without it. SWF playback in 2026 generally requires either the standalone Adobe Flash Player Projector (still downloadable from Adobe's archived debug-tools page) running offline, or the open-source Ruffle browser extension / desktop player, which currently supports most ActionScript 1/2 content and is steadily expanding AS3 coverage.
No. The Foveon X3 sensor stacks three photodiodes per pixel site (sensitive to blue, green, and red light at progressively deeper silicon layers — roughly 0.2 μm, 0.8 μm, and 3.2 μm), producing 12- or 14-bit raw color per channel. SWF's bitmap stream is 8-bit RGBA at best, so the dynamic range and color discrimination unique to Foveon RAW collapse to standard 8-bit-per-channel video. For pixel-perfect Foveon archival, keep the X3F or convert to a 16-bit format like X3F to TIFF.
That is controlled by the Duration option — default is 5 seconds per frame. You can also pick fractional durations (1/60, 1/30, 1/24, 1/10, 1/5, 1/3, 1/2 second) or whole-second values up to 10 seconds. Merrill-series 46 MP captures often look best at 3-5 seconds because viewers want time to actually appreciate the detail; rapid 1/24-second sequences turn a still set into a low-frame-rate motion clip, which is usually not what photographers want.
Yes. Upload all your X3F files and choose "Merge images" under Merge Strategy. They are added to the SWF timeline in the order they appear in the upload list, with the Duration setting controlling per-frame time and the Background Color filling any letterboxing when the source aspect ratio (3:2 on Sigma DSLRs, varies on dp Quattro) does not match the output resolution. To output one SWF per X3F instead, pick "Video per image".
A Foveon X3 sensor records three color samples at every photosite instead of one through a Bayer color filter array, so the raw payload is roughly three times the size of an equivalent-pixel Bayer RAW. That puts SD1 Merrill and DP Merrill X3F at about 50 MB per frame for 46-million-effective-pixel output, and Quattro-series X3F at about 45 MB because Quattro splits the layers as 20 MP top / 5 MP middle / 5 MP bottom. Expect a 50-image shoot to land around 2-2.5 GB on disk before conversion.
No — X3F is a still-image format with no audio, so a SWF generated from X3F frames is silent. If you need a soundtrack on a Flash-era slideshow, the standard workflow is to convert the X3F set to SWF here, then mux a separate audio asset in Adobe Animate or an open-source SWF editor before final export.
Constant Quality holds visual quality steady and lets file size float — best when you want every frame to look the same and do not care if the final SWF is 8 MB or 80 MB. Constraint Quality caps quality so the file stays predictably small — useful when your delivery medium (a CD-ROM partition, a kiosk's onboard storage, a Ruffle bundle) has a hard size budget. For both, "Very High" is a sensible starting preset; drop to "Medium" or "Low" only if Constraint Quality output still exceeds your size target.
xconvert produces SWF via FFmpeg's swf muxer, which writes a SWF7-compatible bitstream — that's compatible with Adobe Flash Player 7 and later, with Ruffle, and with most third-party SWF tooling. If your downstream toolchain insists on a specific older SWF version (some kiosk firmware locks to SWF6) you will likely need to import the resulting SWF into Adobe Animate and re-publish targeting that version, since FFmpeg does not emit SWF6 directly.