Elysia Tools
Navigation
Workflow Playbook
Convert still images, icons, or animated assets into a delivery-friendly format while protecting transparency, frame behavior, dimensions, and preview compatibility.
Hubs
Image conversion becomes unreliable when the source is treated as if every file behaves the same way. Before choosing any target, confirm whether the source is a still image, an icon source, or an animated asset. Then check whether transparency is essential, whether motion must remain intact, and where the final file will be previewed. That simple classification prevents the most common mistakes, such as flattening alpha into a solid matte or exporting animation into a still-only format.
A transparent design asset often needs PNG or WebP, while a compatibility-first handoff may justify JPEG if alpha is irrelevant. Animated assets need even more deliberate choices because GIF, APNG, animated WebP, MP4, and WebM each trade off playback support, compression efficiency, and visual smoothness differently. The right answer depends on where the asset will live: browser UI, mobile app, design handoff, content upload, or archive storage.
One successful file should establish the rule for the rest of the batch. Inspect the converted result in the same environment your audience will use. Check that dimensions stayed correct, transparent edges remain clean, loops still play, and no frames disappeared or reordered. If the output is for icons, verify the generated previews rather than assuming a converted PNG automatically satisfies favicon or app icon packaging.
Batch conversion should not be where you discover the rules. Use it only after a representative sample already proves the source, target, and preview behavior. That keeps image libraries consistent and makes it much easier to explain why a given format was chosen for compatibility, size, and motion or alpha preservation.
Workflow playbook
Start by turning any embedded or exchanged base64 payload into a real image file if needed, then confirm whether you are handling a still image, an icon source, or an animated asset that must keep motion.
Pick the target based on what must survive conversion. Use PNG, WebP, HEIF, or TIFF when transparency or higher fidelity matters; use JPEG only when alpha is irrelevant and broad compatibility matters more than transparency.
For moving assets, decide whether the output should stay as an animated image or become video. Compare loop smoothness, frame visibility, and playback support before settling on GIF, APNG, animated WebP, MP4, or WebM.
Once one sample has been checked, scale the same source-to-target decision to a batch so naming, output format, and repeatability stay consistent instead of mixing incompatible exports.
If the asset needs alpha, avoid JPEG targets and confirm that the chosen destination actually preserves transparency in the expected viewer.
Animated GIF, APNG, animated WebP, MP4, and WebM do not behave identically, so choose based on loop fidelity, playback support, and file size expectations.
Single-file conversions are better for testing assumptions first, while batch work should start only after one verified example proves the settings.
If the output is meant for favicon or app icon use, generate the icon package from a clean PNG source and then inspect the resulting previews for cropping, soft edges, and expected dimensions.