Skip to content
This repository has been archived by the owner. It is now read-only.
An open source Javascript framework for detecting the Adobe Flash Player plugin and embedding Flash (swf) files.
HTML JavaScript ActionScript
Branch: master
Clone or download
pipwerks Merge pull request #41 from paulcoyle/license-file
Add formal licensing file to repository.
Latest commit 232ce6e Jun 17, 2016
Type Name Latest commit message Commit time
Failed to load latest commit information.
swfobject Change comparison to be less strict. Oct 18, 2013
swfobject_generator Updated copyright notice to include 2009 Jan 5, 2009
.jshintrc Added a JSHint config file to check (the current) code style and dete… Aug 12, 2013
LICENSE Add formal licensing file to repository. Jun 16, 2015
README.rdoc Update README.rdoc Jun 15, 2015
bower.json Rename component.json to bower.json, update to current Bower spec Sep 4, 2013



SWFObject is no longer in active development. Flash Player is on the decline, and the authors of SWFObject have moved on to other projects. This project is being left on GitHub for historical purposes.


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


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.

You can’t perform that action at this time.