An open source Javascript framework for detecting the Adobe Flash Player plugin and embedding Flash (swf) files.
JavaScript ActionScript
Switch branches/tags
Nothing to show
Pull request Compare This branch is 1 commit ahead, 29 commits behind swfobject:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.



SWFObject is a free, open-source tool for embedding swf content in websites.

This GitHub edition of SWFObject is our 2.3 beta. The current release – 2.2 – is still available for download at

When 2.3 is made official, we plan to make this GitHub site SWFObject's permanent home.

Since SWFObject 2.3 is in beta, it could very likely have bugs. Please test throughly by visiting and/or by using the 2.3 beta code in your own projects. Please use the uncompressed version of SWFObject until we have ensured there are no bugs.


SWFObject 2.3 introduces many small changes under the hood (almost exclusively aimed at fixing bugs), but the public API is mostly unchanged and completely backwards compatible with SWFObject 2.2. The only two significant changes to the API:

  1. You may now pass an element as an argument in embedSWF (in place of an ID)

  2. You may now use integers in place of number strings in embedSWF (e.g. 9 instead of “9”).



swfobject.embedSWF("myContent.swf", "my-target-element", "300", "120", "10.0.0");


var el = document.getElementById("my-target-element");
swfobject.embedSWF("myContent.swf", el, 300, 120, 10);

Another significant change: SWFObject's approach to dynamic embedding in Internet Explorer has been updated to use a more W3C-friendly way of creating the <object>. Because this is Internet Explorer, a few hacks were required, but the end result is code generated by W3C techniques (document.createElement). This means, among other things, that nodes generated for XHTML documents should properly self close:




<object><param /></object>

Similarly, since the <param> elements are all generated using the same W3C techniques, encoding flashvars should be less troublesome. Developers will no longer need to create separate flashvars encoding workflows for IE and non-IE browsers.