Browser extensions

Remember that you don't have to use browser extensions at all — try that mode too!

Installing extensions

Download and open to install:

• Safari extension 2.0.8
• Chrome extension 2.0.8 — if you want to use it with local files, be sure to enable “Allow access to file URLs” checkbox in Tools > Extensions > LiveReload after installation.
• Firefox extension 2.0.8

Extensions 2.x will be updated automatically.

Using extensions

1. Make sure a compatible server is running (LiveReload 2 for Mac, or one of the older command-line servers)
2. Click the LiveReload button to enable or disable LiveReload.

LiveReload toolbar button is located in the main toolbar in Chrome and Safari, and in the Add-on Toolbar in Firefox (at the bottom).

The icon indicates LiveReload status of the current tab (unavailable / disabled / enabled, connecting / enabled, connected).

If your page already includes LiveReload via a SCRIPT tag, it is considered to be in 'enabled' state initially. You can still disable or reenable it using the toolbar button.

What's new

2.0.5: Enabled autoupdating. Updated bundled livereload.js (for use with old-style clients like guard-livereload and livereload 1.x).

2.0.3: Firefox-only update that fixes handling of frames (see “Cannot find tab for document” support topic).

2.0.2:

• fixed disconnection on each full page reload (yep very lame);
• update livereload.js so that extension, snippet and livereload.js version numbers are now reported to the LR server

2.0.1: fixed support of protocol v6 (i.e. older LR-compatible Ruby gems and older builds of LR2)

2.0.0 (alpha quality!):

• all extensions have been rewritten from scratch
• extensions no longer handle web socket communication — they simply insert a SCRIPT tag into the page, which loads livereload.js, the same one you'd include if you weren't using extensions at all
• all extensions have a toolbar button now (previously Safari was using a context menu item) and use the same icons
• the new live reload protocol is now supported
• the old protocol is supported too, for compatibility with livereload and guard-livereload gems
• servers that implement the new protocol can provide their own livereload.js, thus eliminating the need to update extensions often (and avoiding client/server version mismatches); older servers are served with a bundled version of livereload.js

Open-source

LiveReload browser extensions are open-sourced.