▶️ Make sure the dependencies are fully installed before running any ArchiveBox commands.

ArchiveBox API Reference:

  • CLI Usage: Docs and examples for the ArchiveBox command line interface.

  • Admin UI Usage: Docs and screenshots for the outputted HTML archive interface.

  • Browser Extension Usage: Docs and screenshots for the outputted HTML archive interface.

  • Disk Layout: Description of the archive folder structure and contents.


  • [[Docker]]: Learn about ArchiveBox usage with Docker and Docker Compose

  • [[Configuration]]: Learn about the various archive method options

  • [[Scheduled Archiving]]: Learn how to set up automatic daily archiving

  • [[Publishing Your Archive]]: Learn how to host your archive for others to access

  • [[Troubleshooting]]: Resources if you encounter any problems

CLI Usage

All three of these ways of running ArchiveBox are equivalent and interchangeable:

  • archivebox [subcommand] [...args]
    Using the PyPI package via pip install archivebox

  • docker run -it -v $PWD:/data archivebox/archivebox [subcommand] [...args]
    Using the official Docker image

  • docker-compose run archivebox [subcommand] [...args]
    Using the official Docker image w/ Docker Compose

You can share a single archivebox data directory between Docker and non-Docker instances as well, allowing you to run the server in a container but still execute CLI commands on the host for example.

For more examples see the [[Docker]] page.

Run ArchiveBox with configuration options

You can set environment variables in your shell profile, a config file, or by using the env command.

# via the CLI
archivebox config --set TIMEOUT=3600

# by modifying the config file
nano ArchiveBox.conf
# TIMEOUT=3600

# or by using environment variables
env TIMEOUT=3600 archivebox add ''

See [[Configuration]] page for more details about the available options and ways to pass config.
If you’re using Docker, also make sure to read the Configuration section on the [[Docker]] page.

Import a single URL

archivebox add ''
# or
echo '' | archivebox add

You can also add --depth=1 to any of these commands if you want to recursively archive the URLs and all URLs one hop away. (e.g. all the outlinks on a page + the page).

Import a list of URLs from a text file

cat urls_to_archive.txt | archivebox add
# or
archivebox add < urls_to_archive.txt
# or
curl | archivebox add

You can also pipe in RSS, XML, Netscape, or any of the other supported import formats via stdin.

archivebox add < ~/Downloads/browser_bookmarks_export.html
# or
archivebox add < ~/Downloads/pinboard_bookmarks.json
# or
archivebox add < ~/Downloads/other_links.txt

UI Usage

# configure which areas you want to require login to use vs make publicly available
archivebox config --set PUBLIC_INDEX=False
archivebox config --set PUBLIC_SNAPSHOTS=False
archivebox config --set PUBLIC_ADD_VIEW=False

archivebox manage createsuperuser  # set an admin password to use for any areas requiring login
archivebox server     # start the archivebox web server

open         # open the admin UI in a browser to view your archive

See the Configuration Wiki and Security Wiki for more info…

Or if you prefer to use the static HTML UI instead of the interactive UI provided by the server, you can run archivebox list --html --with-headers > ./index.html and then open ./index.html in a browser. You should see something like this.

You can sort by column, search using the box in the upper right, and see the total number of links at the bottom.

Click the Favicon under the “Files” column to go to the details page for each link.

Explanation of buttons in the web UI - admin snapshots list

Screenshot of buttons at top of Snapshot admin page

A logged-in admin user may perform these operations on one or more snapshots:

  • Search Search text in the Snapshot title, URL, tags, or archived content (supports regex with the default ripgrep search backend, or enable the Sonic full-text search backend in docker-compose.yml and set SEARCH_BACKEND_ENGINE=sonic, SEARCH_BACKEND_HOST, SEARCH_BACKEND_PASSWORD for full-text fuzzy searching)

  • Tags - tag or un-tag snapshots

  • Title Pull the title ( redownload if it was missing, or the title has changed )

  • Pull Download missing/failed outputs/extractors methods ( pdf, wget… etc). Maybe because download failed or interrupted by a reboot or something. This is the default behavior when you add new URL, they will get pulled automatically.

  • Re-Snapshot As the name suggests, re-download the page as a separated unique page. Not the same as pull, this one will create a separate entry, and the page is treated as a new URL ending with the date and time #2020-10-24-08:00

  • Reset Delete all type of output and redownload them. In the contrary of snapshot, this will overwrite the files.

  • Delete Delete a snapshot entirely. This action cannot be undone.

Browser Extension Usage

Get the official @tjhorner/archivebox-exporter Browser Extension:

  1. Set your Add page to allow non-logged-in access archivebox config --set PUBLIC_ADD_VIEW=True (see PUBLIC_ADD_VIEW in the wiki)

  2. Install the extension in your browser:

  1. Set the BASE_URL in the extension to your ArchiveBox server’s URL, e.g.

  2. Test it by archiving some pages from your browser and checking data/logs/* and

chrome web store screenshotbrowser extension config screen

See for more information.

Disk Layout

The OUTPUT_DIR folder (usually whatever folder you run the archivebox command in), contains the UI HTML and archived data with the structure outlined below.

 - data/
   - index.sqlite3        # Main index of all archived URLs
   - ArchiveBox.conf      # Main config file in ini format

   - archive/
      - 155243135/        # Archived links are stored in folders by timestamp
         - index.json     # Index/details page for individual archived link
         - index.html

         # Archive method outputs:
         - warc/
         - media/
         - git/

   - sources/             # Each imported URL list is saved as a copy here
      - stdin-1552291774.txt

For more info about ArchiveBox’s database/filesystem layout and troubleshooting steps:





Large Archives

I’ve found it takes about an hour to download 1000 articles, and they’ll take up roughly 1GB.
Those numbers are from running it single-threaded on my i5 machine with 50mbps down. YMMV.

Storage requirements go up immensely if you’re using FETCH_MEDIA=True and are archiving many pages with audio & video.

You can try to run it in parallel by manually splitting your URLs into separate chunks (though this may not work with database locked errors on slower filesystems):

archivebox add < urls_chunk_1.txt &
archivebox add < urls_chunk_2.txt &
archivebox add < urls_chunk_3.txt &

(though this may not be faster if you have a very large collection/main index)

Users have reported running it with 50k+ bookmarks with success (though it will take more RAM while running).

If you already imported a huge list of bookmarks and want to import only new bookmarks, you can use the ONLY_NEW environment variable. This is useful if you want to import a bookmark dump periodically and want to skip broken links which are already in the index.

For more info about troubleshooting filesystem permissions, performance, or issues when running on a NAS:



SQL Shell Usage

Explore the SQLite3 DB a bit to see whats available using the SQLite3 shell:

cd ~/archivebox
sqlite3 index.sqlite3

# example usage:
SELECT * FROM snapshot;
UPDATE auth_user SET email = '' WHERE username = 'someUsernameHere';

More info:





Python Shell Usage

Explore the Python API a bit to see whats available using the archivebox shell:

Python API Documentation:

$ archivebox shell
[i] [2020-09-17 16:57:07] ArchiveBox v0.4.21: archivebox shell
    > /Users/squash/Documents/opt/ArchiveBox/data

# Shell Plus Model Imports
from core.models import Snapshot
from django.contrib.admin.models import LogEntry
from django.contrib.auth.models import Group, Permission, User
from django.contrib.contenttypes.models import ContentType
from django.contrib.sessions.models import Session
# Shell Plus Django Imports
from django.core.cache import cache
from django.conf import settings
from django.contrib.auth import get_user_model
from django.db import transaction
from django.db.models import Avg, Case, Count, F, Max, Min, Prefetch, Q, Sum, When
from django.utils import timezone
from django.urls import reverse
from django.db.models import Exists, OuterRef, Subquery
# ArchiveBox Imports
from archivebox.core.models import Snapshot, User
from archivebox import *

[i] Welcome to the ArchiveBox Shell!

    Hint: Example use:

# run Python API queries/function calls directly
>>> print(Snapshot.objects.filter(is_archived=True).count())

# get help info on an object or function
>>> help(Snapshot)

# show raw SQL queries run
>>> from django.db import connection
>>> print(connection.queries)

For more info and example usage:






Python API Usage

You can interact with ArchiveBox as a Python library from external scripts or programs.

For example you could create and a script like so:

import os
DATA_DIR = '~/archivebox/data'

# you must import and setup django first to establish a DB connection
from archivebox.config import setup_django

# then you can import all the main functions
from archivebox.main import add, remove, server

add('', index_only=True, out_dir=DATA_DIR)

For more information see: