From Wikipedia, the free encyclopedia
Jump to: navigation, search
Original author(s) Aaron Boodman
Developer(s) Anthony Lieuallen, Johan Sundström,[1] 13 more[2]
Initial release 28 March 2005; 9 years ago (2005-03-28)[3]
Stable release 1.15[4] / 11 February 2014; 2 months ago (2014-02-11)
Written in JavaScript, XUL, CSS
Operating system Cross-platform
Available in English
Type Mozilla extension
License Expat license

Greasemonkey is a Mozilla Firefox extension that allows users to install scripts that make on-the-fly changes to web page content after or before the page is loaded in the browser (also known as augmented browsing).

The changes made to the web pages are executed every time the page is viewed, making them effectively permanent for the user running the script.

Greasemonkey can be used for customizing page appearance, adding new functions to web pages (for example, embedding price comparisons within shopping sites), fixing rendering bugs, combining data from multiple web pages, and numerous other purposes.


The Greasemonkey project began 28 November 2004.[5][6][7]

Technical details[edit]

Greasemonkey user scripts are written in JavaScript and manipulate the contents of a web page using the Document Object Model interface. Scripts are generally written to be either page-specific or domain-specific (applying to all pages within a domain) but may also be tagged to apply to all domains for global browser enhancements. maintains a database of Greasemonkey scripts, and for each, lists the URLs of web pages to which the script pertains.[8] Users of Greasemonkey can write or download scripts and save them to their own personal library. When users visit a website matching a script in their personal script library, Greasemonkey invokes the relevant scripts.

Greasemonkey scripts can modify a webpage in any way that JavaScript allows, with certain Greasemonkey security restrictions. Scripts can also access other web pages and web services via a non-domain-restricted XMLHTTP request, allowing external content to be merged with the original page content.

Scripts are named somename.user.js, and Greasemonkey offers to install any such script when a URL ending in that suffix is requested. Greasemonkey scripts contain metadata which specifies the name of the script, a description, resources required by the script, a namespace URL used to differentiate identically named scripts, and URL patterns for which the script is intended to be invoked or not.

Writing a Greasemonkey script is similar to writing JavaScript for a web page, with some additional allowances such as cross-site XMLHttpRequests. Compared to writing a full-fledged Firefox extension, user scripting is a very modest step up in complexity from basic web programming. However, Greasemonkey scripts are limited due to security restrictions imposed by Mozilla's XPCNativeWrappers. For example, Greasemonkey scripts do not have access to many of Firefox's components, such as the download manager, I/O processes or its main toolbars. Additionally, Greasemonkey scripts run per instance of a matching webpage. Because of this, managing lists of items globally is difficult. However, script writers have been using cookies and Greasemonkey even offers APIs such as GM_getValue and GM_setValue to overcome this.


Greasemonkey is available for Firefox, Flock and Web (formerly called Epiphany). The Greasemonkey extension for Web is part of the Web extensions package. However, this extension is not fully compatible as of release 2.15.1, since some Greasemonkey API functions (e.g. GM_getValue) are unsupported. There are also custom versions for SeaMonkey[9] and Songbird.[10]

Equivalents for other browsers[edit]

Versions 8 and upwards of Opera also have user scripting functionality and are capable of running many Greasemonkey user scripts.[11]

For Internet Explorer, similar functionality is offered by IE7Pro,[12] Sleipnir,[13] and iMacros.

As of February 2010, Chrome has limited "native support" for Greasemonkey scripts.[14] They are internally converted to extensions, and are managed as such. Chrome honors the @include and @exclude directives, and introduces the @match objective as a simplified way to select specific domains/pages specified. In Chrome, scripts that use Firefox-specific functionality will break, and several Greasemonkey features are unavailable.[15] More compatibility is provided by the "TamperMonkey" extension, giving support for GreaseMonkey specific features.[16][17]

On Safari for Mac (and other WebKit applications), there is a SIMBL-managed plug-in called GreaseKit. Since the release of Safari 5 there is an extension called NinjaKit that uses the new API interface.[18] Fluid is a site-specific browser with integrated GreaseKit.

Kango[19] framework allows creating extensions for Firefox, Chrome, Internet Explorer, Opera, Safari using JavaScript only, the code being single for all browsers. Kango supports[20] user scripts.

See also[edit]


External links[edit]