Flash Decompiler Trillix Known issues and FLA format limitations

<< Back to main page

Flash decompilation is a very complex process, and sometimes it is almost impossible to decode the original FLA file structure and contents due to many reasons. Please, get acquainted with the list of known issues concerning SWF to FLA conversion we are aware of.

Once FLA file is compiled into SWF most of the information about its internal structure and object’s order and placements is lost. As a result, SWF movie file size is decreased, which is an advantage for web users. On the other hand, due to such information losses restoring original FLA file from SWF can be a problem.  Situation is worsened by many third-party Flash editing products that do not follow Adobe Flash specifications and introduce their own standards.

These tools may also use the so-called SWF ActionScript which is different from ActionScript you can use in FLA and which cannot be recovered, as FLA format simply doesn’t support it. This may lead to incorrect SWF to FLA conversion and some errors in resulting FLA files. This is a known issue and that is why there’s no guarantee that each and every SWF file can be correctly decompiled.

We are working on reducing the number of conversion errors to the minimum; however, it is not always possible. We hope that you understand this and will help and cooperate with us. You are very welcome to send erroneously converted files to our Support Team for investigation.

Below is the list of known situations that are likely to lead to conversion problems, and are not applicable reasons for refund:

  1. SWF file is compressed, optimized or obfuscated by third-party applications.
  2. SWF file doesn’t satisfy Adobe SWF File Format Specification.
  3. Files compressed with algorithms other than ZLib compression are very likely to lead to erroneous conversion.
  4. Texts objects contain symbols of a national (localized) alphabet.
  5. SWF file may contain font, which is not installed in your system. In this case Flash will ask for a replacement when you open a converted FLA. Otherwise, please, enable conversion of texts into shapes.
  6. FLA format allows placing as many objects on one layer as you want, however, SWF has a limitation of 1 object only. So when converting SWF into FLA objects will be placed into separate layers.
  7. If SWF file does not contain a character map, then Texts objects parsing will lead to the following erroneous texts: “??????”.
  8. When decompiling a Motion Tween, you might need to experiment with “Motion tween” settings.
  9. Some Shape objects that have non-standard fills could be parsed incorrectly. The non-standard fill is the one that is present within a non-closed area that has gaps along its contour. More likely that it was created by a third-party application.
  10. Usually Morph shapes have beginning and ending states. When placing a morph shape on a frame its intermediate state is used. It means that morph shape can be rewound/forwarded into any of its states in SWF. However, it is not possible within FLA format. Morph shapes are placed on the timeline and always run from their beginning state to the ending one.
  11. When you compile your FLA file into SWF the first time, the hierarchy of the layers gets deformed. This peculiarity is important only for Morphs. When a morph is placed on a frame its state is remarked and written. It leads to the problem when a series of morphs can be “split” into several layers. Such frames cannot be correctly converted into FLA at this stage.
  12. Action buttons in FLA file are set when you place them on frames. In SWF files actions are stored in buttons themselves, that’s why each button will be represented as a separate instance in FLA, even if they are different in ActionScript only.
  13. We do not decompile captivate projectors (EXE), projectors not created in Adobe Flash.
  14. Current build of Flash Decompiler doesn’t feature the replacement images with 8-bit PNG images with Alpha. We are right now working on these images format support. Currently it is recommended to use 32-bit PNG images for SWF file editing in Flash Decompiler Trillix.
  15. Sounds with “Nellymoser Asao” codec cannot be extracted properly.
  16. Some problems may occur while converting video with “On2 Truemotion VP6 bistream (with alpha)” to FLA format.
  17. In some cases video which is extracted to AVI format can be played incorrectly.
  18. Flash Decompiler may hang when you replace sounds by MP3 in SWF. Such problems may occur when the size of your sounds is very large.
  19. When the original FLA file is published into SWF format all the original scenes are joined into one scene. Almost no information is transferred to the output SWF file about the original scenes. This information is impossible to be retrieved in most cases. That is the reason why the output FLA file decompiled from the SWF file has only one scene. This fact won’t influence the SWF file functionality after it is published from FLA.
  20. Links editor allows editing statically embedded links only (but not those, which are formed in AS dynamically or located in HTML).
  21. Code (in AS 3.0), written into timeline and movie clips, is placed into separate AS classes by Adobe Flash when published into SWF. In most cases it doesn`t cause any problems. But sometimes the original file developer may give such sprite a name (in Linkage settings, Class field) which will be treated incorrectly by AS (e.g., a name starting from a digit or a name equal to AS keyword). Adobe Flash doesn`t check the name, so there will be no problems during compilation. But during republishing after conversion, AS compiler checks the name and may give error message.Such files need to be corrected manually: one should move the code from functions like “public function frame1()” to the corresponding frame on movie clip timeline, and then delete these AS files.
  22. Flash Decompiler does not support Flex modules, dynamically loadable SWF files.
  23. If a Flex file was created using locales, not installed on your machine, then after Flex file conversion and further recompilation in Adobe Flex Builder you will get an error message. For example: “Unable to open ‘C:\Program Files\Adobe\Flex Builder 3\sdks\3.2.0\frameworks\locale\fr_FR-locale”. Refer to our Knowledge Base to know how to resolve this issue.
  24. If a locale, which is default for your Adobe Flex Builder, is not present in the resulting Flex Builder project, you will get an error message, while recompiling this Flex Builder project in Adobe Flex Builder. For example: “Unable to open ‘C:\Users\username\Documents\Flex Builder 3\index.swf.flex\locale\en_US”. Refer to our Knowledge Base to know how to resolve this issue.
  25. Text Layout Framework (TLF) texts are currently supported by Flash Decompiler Trillix only basically.
  26. SWF files, containing binary data, cannot be correctly converted into FLA currently.
  27. When AIR SWF file is converted into Flex project using Flash Decompiler Trillix, the resulting Flex project cannot be opened in Flex Builder 3. However, you can open and work with it in Flex Builder 4 without problems. It is caused by functional peculiarities of Flex Builder 3. If you still need to open the resulting Flex project in Flex Builder 3, we can propose the following workaround:Once the SWF file is decompiled using Flash Decompiler Trillix, find .project file in the resulting folder. Replace the following strings:






  28. Currently Flash Decompiler Trillix does not support Flex Mobile Projects.

<< Back to main page