PPM to SWF Converter

Assembling a PPM Sequence Into a Flash Movie

PPM files usually arrive in numbered batches. Ray tracers, plotting libraries, simulation codes, scanner drivers and PostScript rasterisers all write Portable Pixmap because it takes about ten lines of code to emit — a two-line ASCII header followed by red, green and blue bytes — and they write one per frame. SWF is what you need when the destination is a Flash-era system: legacy courseware and LMS packages, kiosk and signage players, an Adobe Animate project, or a Flash archive kept playable through the Ruffle emulator.

This page takes the batch and produces the movie. The mechanics are simple but a few of them are not obvious, so this walkthrough covers what happens to each frame on the way in.

How to Convert PPM to SWF

1. Upload Your PPM Files: Drag the whole numbered batch onto the page or click "Add Files". Binary P6, ASCII P3 and 16-bit files with a Maxval above 255 are all read. Upload order is playback order, so make sure the filenames sort the way the frames should run — zero-padded numbering (frame0001.ppm) is what you want, not frame1.ppm through frame10.ppm.
2. Choose a Merge Strategy and Image Duration: Merge strategy opens on Merge images, which is what you want for a sequence — one movie containing every frame. Video per image writes a separate .swf for each file instead. Image Duration opens at 5 seconds per frame, which is a slideshow pace; a rendered animation wants 1/24, 1/30 or 1/60 second.
3. Set the Codec and Quality: Video Codec opens on FLV — Sorenson Spark, the Flash-native codec — with MJPEG as the alternative. The control that actually governs quality here is Constant Quality, whose slider runs 1 to 31 where lower is better; 2 to 4 gives a clean result. The Quality Preset dropdown has nothing to work with on a still-image source, as explained below.
4. Set the Frame Size and Background, Then Convert: Video resolution opens on Keep original; Fixed Resolutions gives an exact frame such as 1280 x 720, while Preset Resolutions set only the height. Background Color opens on White. Click Convert. Files are uploaded over an encrypted connection, processed on our servers and deleted automatically after a few hours — no sign-up, no watermark.

What Happens to Each Frame

The output is silent. On an image source the audio controls are not rendered at all, because there is no audio stream to configure — add a soundtrack in Animate or an editor afterwards.

Getting the Timing Right for a Rendered Sequence

Image Duration is the only timing control and it applies to every frame equally. Work backwards from the playback rate you want:

• 1/60 second per frame gives 60 frames per second, which is what a simulation rendered at 60 fps needs to play back at real speed.
• 1/30 or 1/24 second are the ordinary video rates. 240 frames at 1/24 second is a ten-second animation.
• 0.2 or 0.3 second reads as deliberate stepping — good for a turntable, a stop-motion sequence or a plot that changes one variable at a time.
• 1 to 10 seconds is slideshow territory, which is what the default of 5 seconds assumes.

If your renderer produced frames at a fixed rate and you want them played back at that rate, the arithmetic is simply one divided by the frame rate. Nothing here resamples or interpolates: every uploaded PPM becomes exactly one frame, and no frames are invented or dropped.

Common Problems and Fixes

Frequently Asked Questions

Why does the Quality Preset dropdown do nothing?

Because it works by scaling the source's own bitrate, and a still image does not have one. On video sources the preset multiplies the input rate to get a target; on an image source that figure is zero, so on the quantiser-based codecs this page offers there is nothing to scale and the setting does not reach the encoder in a meaningful way. Use Constant Quality instead, where the 1-to-31 slider maps straight onto the encoder's quantiser — 1 is nearly lossless, 31 is heavily compressed, and 2 to 4 is the useful range.

Should I choose FLV or MJPEG?

FLV in almost every case. It codes each frame as a difference from the previous one, which is a very large saving on any sequence where the picture is similar from frame to frame — and an enormous one on held stills, where a measured test showed a five-second hold at roughly a tenth the size of the MJPEG equivalent. FLV is also what Ruffle's decoder is built for. MJPEG's case is narrow: it stores every frame as an independent JPEG, which helps only if something downstream needs to pull single frames out of the file.

What plays a SWF file now that Flash is gone?

Adobe ended Flash Player support on 31 December 2020 and began blocking Flash content on 12 January 2021, so browsers do not play these natively any more. Ruffle is the practical answer for playback — it runs as a browser extension, a desktop application and a self-hosted web player, and its video support is built on a Rust H.263 decoder written for exactly the Sorenson-flavour streams this page produces. VLC and mpv will also open the video inside a SWF, and Adobe Animate still imports the format.

Does the pipeline read plain ASCII P3 files?

Yes, along with binary P6 and 16-bit files with a Maxval above 255. P3 files write every sample as an ASCII decimal number, so they are typically three to four times larger than the equivalent P6 and slower to upload. If you control the code that writes them, P6 is the better choice for everything except human inspection.

How many PPM files can I put in one movie?

There is no fixed count limit, but PPM is uncompressed — three bytes per pixel at 8-bit, six at 16-bit — so a long sequence becomes a very large upload quickly. A 1920 x 1080 frame is 6.2 MB before compression, so 240 of them is about 1.5 GB. If the sequence is long, either render at the size you actually want to publish or compress the frames to PNG first; the upload is normally the slowest part of the job by a wide margin.

Will a 16-bit PPM keep its extra precision?

No. Video is 8 bits per channel throughout the encoding chain, so a Maxval above 255 is reduced during the decode step. That is rarely a practical problem for playback, but it does mean a high-dynamic-range render will show banding in smooth gradients that was not visible in the source. If the precision matters, keep the PPMs, or convert the individual frames to PPM to PNG, which stores 16 bits per channel.

Why is my animation stretched or letterboxed?

Because the movie frame and the image frame do not match. On "Keep original" the movie takes its dimensions from the first image you uploaded, and everything else is fitted inside that with the Background Color filling the difference. If you set a Fixed Resolution, the same fitting happens against that frame instead. The clean fix is to render the whole sequence at the aspect ratio you intend to publish, and to choose a Fixed Resolution that matches it.

Is SWF the right target, or should I use something else?

Only choose SWF if a Flash-era system is genuinely the destination. For anything with a modern audience — a website, a phone, a television, a media server, a video platform — PPM to MP4 assembles exactly the same sequence with H.264 video that every player decodes, at a better size and without needing an emulator. SWF is the answer to "this legacy system only accepts SWF", not to "I need a video from these renders".

How are my files handled during conversion?

Your PPM files are uploaded over an encrypted connection, processed on our servers, and both the uploads and the finished movie are deleted automatically after a few hours. Nothing is shared or made public, and there is no sign-up, no watermark and no account required.