From ArchWiki

Luakit is an extremely fast, lightweight and flexible web browser using the webkit engine. It is customizable through lua scripts and fully usable with keyboard shortcuts. It uses GTK 3 and WebKit2GTK.


Install the luakit package or luakit-gitAUR for the development version as the official website recommends.

Basic usage

This article or section needs language, wiki syntax or style improvements. See Help:Style for reference.

Reason: Do we really need to duplicate upstream or internal documentation? (Discuss in Talk:Luakit)
Note: Shortcuts are listed in a special page accessible with the :binds command.

Press : to access the command prompt. You can do nearly everything from there. Use Tab to autocomplete commands.

Use the :help command to get information on the available keyboard shortcuts and what they do. (To see how the action for a particular keyboard shortcut is implemented in Lua, click anywhere in its help text.)

To quit, use the :quit command, or press Shift+z followed by Shift+q. You can also close the browser while remembering the session (i.e. restoring the tabs) by using the :writequit command instead, or pressing Shift+z twice.


  • Press o to open a prompt with the :open command and enter the URI you want. Press Shift+o to edit the current URI.
  • If it is not a recognized URI, Luakit will use the default search engine. See #Custom search engines.
  • Specify which search engine to use by prefixing the entry with the appropriate keywork (e.g. :open google foobar will search foobar on Google).
  • Use common shortcuts to navigate. For emacs and vim aficionados, some of their regular shortcuts are provided. You can use the mouse as well.
  • Use f to display the index of all visible links. Enter the appropriate number or a part of the string to open the link.
  • Use Shift+f instead to open link in a new tab.
  • Press Ctrl+t to open a new tab, Ctrl+w to close it. Press t to prompt for an URI to be opened in a new tab, and Shift+t to edit the current URI in a new tab.
  • Press w to prompt for an URI to be opened in a new window, and Shift+w to edit the current URI in a new window.
  • Switch from one tab to another by pressing g followed by t or Shift+t, or use Ctrl+PageUp and Ctrl+PageDown.
  • You can switch to a specific tab with Alt+number.
  • Use Shift+h to go back in the browser history.
  • Use Shift+l to go forward in the browser history.
  • Reorder the tabs with < and >.
  • Reload the page with r, stop the loading with Ctrl+c.
  • Re-open last closed tab with u.
  • Open downloads page by pressing g followed by d (or Shift+d for a new tab).
  • Copy URI to primary selection with y.
  • View page source code with :viewsource. Return to normal view with :viewsource!.
  • View image source by pressing ; followed by i (or Shift+i for new tab).
  • Inspect elements with :inspect. Repeat to open in a new window. Disable inspector with :inspect!.

Input fields

Many webpages have editable elements like dropdown lists, checkboxes, text fields and so on. While they work perfectly with the mouse, you may encounter some troubles using the follow commands. In such a case, pressing the arrow keys may help. Alternatively, the g i shortcut can be used to focus input.


If enabled (default configuration), bookmarks can be used from within Luakit.

  • The :bookmarks command opens the bookmarks page. (Shortcut: g followed by b, or Shift+b for a new tab).
  • The :bookmark [URI [tags]] command adds the URI specified (or the current tab's URI, if omitted) to the bookmarks by specified tags. Starting from version 2012-09-13-r1, bookmarks page will be opened (new tab) in new bookmark editing mode before saving. (Shortcut: Shift+b).


Configuration is done in ~/.config/luakit/userconf.lua. It is not necessary anymore to copy and modify rc.lua. Some settings can also be modified with the :settings command, unless you set them in userconf.lua with:

local settings = require "settings"
settings.example = "some value"

Key bindings

Most bindings will require some knowledge of Luakit, but you can at least do simple things rebinding:

local modes = require "modes"

-- Creates new bindings from old ones.
modes.remap_binds("normal", -- This is the mode in which the bindings are active.
  --  new     old     removes the old binding (defaults to false)
     {"O",    "t",    true},
  -- define as many as you wish
    {"Control-=", "zi"},

To bind keys to commands, you can use the following template:

modes.add_binds("normal", {
-- {"<key>",
--  "<description>",
--  function (w) w:enter_cmd("<command>") end}
  {"O", "Open URL in a new tab.",
   function (w) w:enter_cmd(":tabopen ") end},

For inspiration, see /usr/share/luakit/lib/binds.lua, where the default bindings are defined.


Set your homepage as follows:

settings.window.home_page = ""

Custom search engines

To search with the default search engine, press o and type the phrases. To search with a different engine, type its name after o and then the phrases.

You can virtually add any search engine you want. Make a search on the website you want and copy paste the URI to the Luakit configuration by replacing the searched terms with an %s. Example:

local engines = settings.window.search_engines
engines.aur          = ""           = ""
engines.googleseceng = ""

The variable is used as a keyword for the :open command in Luakit.

Set the defaut search engine by using this same keyword:

engines.default = search_engines.aur

Instead of strings, you can defined search engines as functions that return a string. For instance, here is a Wikipedia search engine that lets you specify a language (defaulting to English):

engines.wikipedia = function (arg)
  local l, s = arg:match("^(%a%a):%s*(.+)")
  if l then
    return "https://" .. l .. "" .. s
    return "" .. arg

If called as :open wikipedia arch linux, this will open the Arch Linux page on the English Wikipedia; with :open wikipedia fr: arch linux, this will use the French Wikipedia instead.

Download location

To specify download location:

require "downloads"
downloads.default_dir = os.getenv("HOME") .. "/mydir"

Default location is $XDG_DOWNLOAD_DIR if it exists, $HOME/downloads otherwise.


Adblock is loaded by default, but you need to:

  • Fetch an adblock-compatible list, like Easylist, and save it to ~/.local/share/luakit/adblock.
  • Restart Luakit to load the extension.
  • Use :adblock-list-enable number command within Luakit to turn Adblock's list(s) you downloaded on Adblock itself becomes enabled on startup.

Full info on enabled lists and AdBlock state can be found using :adblock or g Shift+a at luakit://adblock/ internal page, if the adblock_chrome module is enabled, which is not a mandatory part.

Note: For Adblock to run in normal mode, easylist.txt and any others must be placed in ~/.local/share/luakit/adblock

Bookmarks management


Starting from version 2012.09.13, Luakit bookmarks are stored in an SQLite database: ~/.local/share/luakit/bookmarks.db.

You can put a symbolic link in place of the default file to store your bookmarks anywhere on your machine. This way if your are using a cloud sync application like Dropbox, you can keep your bookmarks synchronized between your different computers.

Converting plain text bookmarks to SQLite format

Bookmarks were stored in a simple plain text file: ~/.local/share/luakit/bookmarks. Each line is a bookmark. It is composed of 2 fields, the link and the group which are separated by a tab character.

Warning: If spaces are inserted instead of tabulation character, the link will not be properly bookmarked.
Note: Groups and links are alphabetically sorted, so there is no need to do it manually.

To use bookmarks with the latest Luakit release, the file must be converted. A sample Lua script will do that:

local usage = [[Usage: luakit -c bookmarks_plain_to_sqlite.lua [bookmark plaintext path] [bookmark db path]

local old_db_path, new_db_path = unpack(uris)

if not old_db_path or not new_db_path then

-- One-pass file read into 'data' var.
old_db = assert(, "r"))
local data = old_db:read("*all")

-- Init new_db, otherwise sqlite queries will fail.
new_db = sqlite3{ filename = new_db_path }

-- Fill
local url,tag

for line in data:gmatch("[^\n]*\n?") do

   if string.len(line) > 1 then

      print ("["..line.."]")

      -- Get url and tag (if present) from first line.
      _, _, url, tag = string.find(line, "([^\n\t]+)\t*([^\n]*)\n?")

      -- Optional yet convenient output.

      -- DB insertion. Nothing will be overwritten. If URL and/or tag already exists, then a double is created.
      new_db:exec("INSERT INTO bookmarks VALUES (NULL, ?, ?, ?, ?, ?, ?)", 
                     url, "", "", tag or "",
                     os.time(), os.time()

print("Import finished.")
print("\nVacuuming database...")
new_db:exec "VACUUM"
print("Vacuum done.")


As stated at beginning of the script, it must be ran with Luakit:

$ luakit -c bookmarks_plain_to_sqlite.lua path/to/plaintext/bookmark path/to/db

The old plaintext bookmarks will be left unchanged. If the DB bookmarks do not exist, the file will be created. If it exists, do not worry, none of the previous bookmarks will be touched. However, this behaviour implies that you might get some doubles.

Import from Firefox

To import bookmarks from Firefox, first they must be exported to an HTML file using its bookmarks manager. After that the XML file can be converted to a Luakit format.

The following one-line awk command will do that:

$ cat bookmarks.html | awk '
{gsub(/\"/," ")}
/<\/H3>/{FS=">";gsub(/</,">");og=g;g=$(NF-2);FS=" "}
/<DL>/{x++;if(x>= 3)gl[x-3]=g}
/HREF/{gsub(/</," ");gsub(/>/," ");if(g!=""){if(og!=g){printf "\n";og=g};printf "%s\t",$4;if(x>=3){for(i=0;i<=x-4;i++){printf "%s-",gl[i]}printf "%s\n",gl[x-3]}else{printf "\n"}}}'

The more readable version of the script:

# Notes: 'folders' for Firefox bookmarks mean 'groups' for Luakit.

# Put spaces where it is needed to delimit words properly.
{gsub(/\"/," ")}

# Since the folder name may have spaces, delimiter must be ">" here.
/<\/H3>/ {
    FS=" "

# Each time a <DL> is encountered, it means we step into a subfolder.
# 'count' is the depth level.
# Base level starts at 2 (Firefox fault).
# 'groupline' is an array of all parent folders.
/<DL>/ {
    if ( count >= 3 )

# On </DL>, we step out.
# If if return to the base level (i.e. not in a folder), then we give 'group' a fake name different
# from 'oldgroup' to make sure a line will be skipped (see below).
/<\/DL>/ {
    if( count == 2 )

# The bookmark name.
# If oldgroup is different than group, (i.e. folder changed) then we skip a line.
# If we are in a folder, then we print the group name, i.e. all parents plus the current folder
# separated by an hyphen.
/HREF/ {
    gsub(/</," ")
    gsub(/>/," ")
    if (group != "")
        if(oldgroup != group)
            printf "\n"
        printf "%s\t",$4
        if ( count >= 3 )
            for ( i=0 ; i <= count-4 ; i++ )
            {printf "%s-" , groupline[i]}
            printf "%s" , groupline[count-3]
        printf "\n"

Run it with

$ awk -f ff2lk.awk bookmarks.html >> bookmarks

Then convert the generated plain text bookmarks to the SQLite format as described at #Converting plain text bookmarks to SQLite format.

Export bookmarks

The following script let you export Luakit bookmarks from its SQLite format to a plain text file. The resulting file may be suitable for other web browsers, or may be easily parsed by import scripts.


local sep = " "


local usage = [[Usage: luakit -c bookmarks_sqlite_to_plain.lua [bookmark db path] [bookmark plain path]

DB scheme is

    bookmarks (
        uri TEXT NOT NULL,
        title TEXT NOT NULL,
        desc TEXT NOT NULL,
        tags TEXT NOT NULL,
        created INTEGER,
        modified INTEGER

local old_db_path, new_db_path = unpack(uris)

if not old_db_path or not new_db_path then

-- One-pass file read into 'data' var.
new_db = assert(, "w"))

-- Open old_db
old_db = sqlite3{ filename = old_db_path }

-- Load all db values to a string variable.
local rows = old_db:exec [[ SELECT * FROM bookmarks ]]

-- Iterate over all entries.
-- Note: it could be faster to use one single concatenation for all entries, but
-- it would be much more code and not so flexible. It is desirable to focus on
-- clarity. After all, only a few hundred lines are handled.
for _, b in ipairs(rows) do

   -- Change %q for %s to remove double quotes if needed.
   -- You can toggle the desired fields with comments.
   local outputstr = 
      string.format("%q%s", b.uri or "", sep) .. 
      string.format("%q%s", b.title or "", sep) ..
      string.format("%q%s", b.desc or "", sep) ..
      string.format("%q%s- ", b.tags or "", sep) ..
      ((b.created or "" ) .. sep) ..
      ((b.modified or "" ) .. sep) ..

   -- Write entry to file.

print("Export done.")



As stated at beginning of the script, it must be ran with Luakit:

$ luakit -c bookmarks_plain_to_sqlite.lua path/to/plaintext/bookmarks path/to/database


Once Tor has been setup, simply run:

$ torsocks luakit --nounique
Warning: To be sure of anonymity, you also need to change settings within Luakit, such as disabling Flash and changing the useragent string.

Custom CSS

Locate the styles sub-directory within luakit's data storage directory. Normally, this is located at ~/.local/share/luakit/styles/. Create the directory if it does not already exist. Move any CSS rules to a new file within that directory. The filename must end in .css. Make sure you specify which sites your stylesheet should apply to. The way to do this is to use @-moz-document rules. The Stylish wiki page Applying styles to specific sites may be helpful. Run :styles-reload to detect new stylesheet files and reload any changes to existing stylesheet files; it is not necessary to restart luakit.

To open the styles menu, run the command :styles-list. Here you can enable/disable stylesheets, open stylesheets in your text editor, and view which stylesheets are active.

If a stylesheet is disabled for all pages, its state will be listed as "Disabled". If a stylesheet is enabled for all pages, but does not apply to the current page, its state will be listed as "Enabled". If a stylesheet is enbaled for all pages _and_ it applies to the current page, its state will be listed as "Active".

See also