Recently there has been tons of activity on the Animated SVG exporter for Flash Pro.



Here are some recently added features. Before I explain them, here’s an example of most of the new features in use, thanks to Jazza Studios for the animation. There are a few small issues with it but you get how nice the output is looking now.

(Weighs about 1.4mb gzipped, have patience)

Keep in mind that the only Javascript used in this is a few tiny triggers for the audio.

As I haven’t used a SMIL polyfill this won’t run in current versions of IE (check out my post here for adding IE support).

Audio support

Audio used in your animation is now output into your file. By default the sounds are saved as external files and referenced by the SVG. Note that this feature uses a very small amount of Javascript to trigger the sound effect, which may not be compatible with pure SVG players.

Image & Audio Embedding

These two new options allow for embedding referenced image and audio files directly into the SVG, allowing for a fully contained SVG file. Note that unlike when exporting a SWF from flash, there is no compression applied to these resources when exporting an SVG. All compression should be done on the assets before importing into Flash Pro.

SVG Scaling

When loading an SVG into an HTML document, it often important to specify how the SVG scales within it’s container. This option allows for three different settings: None, Contain within bounds & Crop to bounds.

Animated ViewBox

This is a powerful feature that allows you to animate the SVG viewBox, effectively moving the ‘camera’ around the animation scene. Use this by turning on the “Use animated viewBox” setting and animating an instance on your timeline with the name “viewBox”. The instance should have the same aspect ratio as your document and transforms like rotation and skew will be ignored on the instance.

This release also contain a bunch of bug fixes, notably for longer animations.

Note to CS users

None of these new features are accessible in the old CS version of the tool. I might have time in the future to add support, except for the two embedding options, which rely on CC APIs that are not accessible in CS.