View on GitHub


🗃 Open source self-hosted web archiving. Takes URLs/browser history/bookmarks/Pocket/Pinboard/etc., saves HTML, JS, PDFs, media, and more...

Open-source self-hosted web archiving.

▶️ Quickstart | Demo | GitHub | Documentation | Info & Motivation | Community | Roadmap

ArchiveBox is a powerful, self-hosted internet archiving solution to collect, save, and view websites offline.

Without active preservation effort, everything on the internet eventually dissapears or degrades. does a great job as a free central archive, but they require all archives to be public, and they can’t save every type of content.

ArchiveBox is an open source tool that helps you archive web content on your own (or privately within an organization): save copies of browser bookmarks, preserve evidence for legal cases, backup photos from FB / Insta / Flickr, download your media from YT / Soundcloud / etc., snapshot research papers & academic citations, and more…

➡️ Use ArchiveBox as a command-line package and/or self-hosted web app on Linux, macOS, or in Docker.

📥 You can feed ArchiveBox URLs one at a time, or schedule regular imports from browser bookmarks or history, feeds like RSS, bookmark services like Pocket/Pinboard, and more. See input formats for a full list.

snapshot detail page

💾 It saves snapshots of the URLs you feed it in several redundant formats.
It also detects any content featured inside each webpage & extracts it out into a folder:

It uses normal filesystem folders to organize archives (no complicated proprietary formats), and offers a CLI + web UI.

🏛️ ArchiveBox is used by many professionals and hobbyists who save content off the web, for example:

The goal is to sleep soundly knowing the part of the internet you care about will be automatically preserved in durable, easily accessible formats for decades after it goes down.

bookshelf graphic   logo   bookshelf graphic

Demo | Screenshots | Usage
. . . . . . . . . . . . . . . . . . . . . . . . . . . .

📦  Get ArchiveBox with docker / apt / brew / pip3 / nix / etc. (see Quickstart below).

# Get ArchiveBox with Docker or Docker Compose (recommended)
docker run -v $PWD/data:/data -it archivebox/archivebox:dev init --setup

# Or install with your preferred package manager (see Quickstart below for apt, brew, and more)
pip3 install archivebox

# Or use the optional auto setup script to install it
curl -sSL '' | sh

🔢 Example usage: adding links to archive.

archivebox add ''                                   # add URLs one at a time
archivebox add < ~/Downloads/bookmarks.json                            # or pipe in URLs in any text-based format
archivebox schedule --every=day --depth=1  # or auto-import URLs regularly on a schedule

🔢 Example usage: viewing the archived content.

archivebox server            # use the interactive web UI
archivebox list ''     # use the CLI commands (--help for more)
ls ./archive/*/index.json                 # or browse directly via the filesystem

cli init screenshot cli init screenshot server snapshot admin screenshot server snapshot details page screenshot

Key Features

🤝 Professional Integration

Contact us if your non-profit institution/org wants to use ArchiveBox professionally.

All our work is open-source and primarily geared towards non-profits.
Support/consulting pays for hosting and funds new ArchiveBox open-source development.



🖥  Supported OSs: Linux/BSD, macOS, Windows (Docker)   👾  CPUs: amd64 (x86_64), arm64 (arm8), arm7 (raspi>=3) Note: On arm7, the playwright package, provides easy chromium management, is not yet available. Do it manually with alternative methods.

✳️  Easy Setup

Docker docker-compose (macOS/Linux/Windows)   👈  recommended   (click to expand)
👍 Docker Compose is recommended for the easiest install/update UX + best security + all the extras working out-of-the-box.

  1. Install Docker and Docker Compose on your system (if not already installed).
  2. Download the docker-compose.yml file into a new empty directory (can be anywhere).
    mkdir ~/archivebox && cd ~/archivebox
    curl -O ''
  3. Run the initial setup and create an admin user.
    docker compose run archivebox init --setup
  4. Optional: Start the server then login to the Web UI ⇢ Admin.
    docker compose up
    # completely optional, CLI can always be used without running a server
    # docker compose run [-T] archivebox [subcommand] [--args]
See below for more usage examples using the CLI, Web UI, or filesystem/SQL/Python to manage your archive.

Docker docker run (macOS/Linux/Windows)
  1. Install Docker on your system (if not already installed).
  2. Create a new empty directory and initialize your collection (can be anywhere).
    mkdir ~/archivebox && cd ~/archivebox
    docker run -v $PWD:/data -it archivebox/archivebox init --setup
  3. Optional: Start the server then login to the Web UI ⇢ Admin.
    docker run -v $PWD:/data -p 8000:8000 archivebox/archivebox
    # completely optional, CLI can always be used without running a server
    # docker run -v $PWD:/data -it [subcommand] [--args]
See below for more usage examples using the CLI, Web UI, or filesystem/SQL/Python to manage your archive.

curl sh automatic setup script bash auto-setup script (macOS/Linux)
  1. Install Docker on your system (optional, highly recommended but not required).
  2. Run the automatic setup script.
    curl -sSL '' | sh
See below for more usage examples using the CLI, Web UI, or filesystem/SQL/Python to manage your archive.
See for the source code of the auto-install script.
See "Against curl | sh as an install method" blog post for my thoughts on the shortcomings of this install method.

🛠  Package Manager Setup

aptitude apt (Ubuntu/Debian)
  1. Add the ArchiveBox repository to your sources.
    echo "deb focal main" | sudo tee /etc/apt/sources.list.d/archivebox.list
    sudo apt-key adv --keyserver --recv-keys C258F79DCC02E369
    sudo apt update
  2. Install the ArchiveBox package using apt.
    sudo apt install archivebox
    sudo python3 -m pip install --upgrade --ignore-installed archivebox   # pip needed because apt only provides a broken older version of Django
  3. Create a new empty directory and initialize your collection (can be anywhere).
    mkdir ~/archivebox && cd ~/archivebox
    archivebox init --setup           # if any problems, install with pip instead
    Note: If you encounter issues with NPM/NodeJS, install a more recent version.

  4. Optional: Start the server then login to the Web UI ⇢ Admin.
    archivebox server
    # completely optional, CLI can always be used without running a server
    # archivebox [subcommand] [--args]
See below for more usage examples using the CLI, Web UI, or filesystem/SQL/Python to manage your archive.
See the debian-archivebox repo for more details about this distribution.

homebrew brew (macOS)
  1. Install Homebrew on your system (if not already installed).
  2. Install the ArchiveBox package using brew.
    brew tap archivebox/archivebox
    brew install archivebox
  3. Create a new empty directory and initialize your collection (can be anywhere).
    mkdir ~/archivebox && cd ~/archivebox
    archivebox init --setup         # if any problems, install with pip instead
  4. Optional: Start the server then login to the Web UI ⇢ Admin.
    archivebox server
    # completely optional, CLI can always be used without running a server
    # archivebox [subcommand] [--args]
See below for more usage examples using the CLI, Web UI, or filesystem/SQL/Python to manage your archive.
See the homebrew-archivebox repo for more details about this distribution.

Pip pip (macOS/Linux/BSD)
  1. Install Python >= v3.9 and Node >= v18 on your system (if not already installed).
  2. Install the ArchiveBox package using pip3.
    pip3 install archivebox
  3. Create a new empty directory and initialize your collection (can be anywhere).
    mkdir ~/archivebox && cd ~/archivebox
    archivebox init --setup
    # install any missing extras like wget/git/ripgrep/etc. manually as needed
  4. Optional: Start the server then login to the Web UI ⇢ Admin.
    archivebox server
    # completely optional, CLI can always be used without running a server
    # archivebox [subcommand] [--args]
See below for more usage examples using the CLI, Web UI, or filesystem/SQL/Python to manage your archive.
See the pip-archivebox repo for more details about this distribution.

Arch pacman / FreeBSD pkg / Nix nix (Arch/FreeBSD/NixOS/more)
> [!WARNING] > *These are contributed by external volunteers and may lag behind the official `pip` channel.* See below for usage examples using the CLI, Web UI, or filesystem/SQL/Python to manage your archive.

🎗  Other Options

Docker docker + Electron electron Desktop App (macOS/Linux/Windows)
  1. Install Docker on your system (if not already installed).
  2. Download a binary release for your OS or build the native app from source

✨ Alpha (contributors wanted!): for more info, see the: Electron ArchiveBox repo.
paid Paid hosting solutions (cloud VPS)
For more discussion on managed and paid hosting options see here: Issue #531.

➡️  Next Steps


⚡️  CLI Usage

# archivebox [subcommand] [--args]
# docker-compose run archivebox [subcommand] [--args]
# docker run -v $PWD:/data -it [subcommand] [--args]

archivebox init --setup      # safe to run init multiple times (also how you update versions)
archivebox --version
archivebox help

🖥  Web UI Usage

archivebox manage createsuperuser  # set an admin password
archivebox server     # open to view it

# you can also configure whether or not login is required for most features
archivebox config --set PUBLIC_INDEX=False
archivebox config --set PUBLIC_SNAPSHOTS=False
archivebox config --set PUBLIC_ADD_VIEW=False

🗄  SQL/Python/Filesystem Usage

sqlite3 ./index.sqlite3    # run SQL queries on your index
archivebox shell           # explore the Python API in a REPL
ls ./archive/*/index.html  # or inspect snapshots on the filesystem


. . . . . . . . . . . . . . . . . . . . . . . . . . . .

Usage | Configuration | Caveats



Input Formats

ArchiveBox supports many input formats for URLs, including Pocket & Pinboard exports, Browser bookmarks, Browser history, plain text, HTML, markdown, and more!

Click these links for instructions on how to prepare your links from these sources:

# archivebox add --help
archivebox add ''
archivebox add < ~/Downloads/firefox_bookmarks_export.html
archivebox add --depth=1 ''
echo '' | archivebox add
echo 'any_text_with [urls]( in it' | archivebox add

# if using Docker, add -i when piping stdin:
# echo '' | docker run -v $PWD:/data -i archivebox/archivebox add
# if using Docker Compose, add -T when piping stdin / stdout:
# echo '' | docker compose run -T archivebox add

See the Usage: CLI page for documentation and examples.

It also includes a built-in scheduled import feature with archivebox schedule and browser bookmarklet, so you can pull in URLs from RSS feeds, websites, or the filesystem regularly/on-demand.

Output Formats

Inside each Snapshot folder, ArchiveBox saves these different types of extractor outputs as plain files:


It does everything out-of-the-box by default, but you can disable or tweak individual archive methods via environment variables / config.


ArchiveBox can be configured via environment variables, by using the archivebox config CLI, or by editing the ArchiveBox.conf config file directly.

archivebox config                               # view the entire config
archivebox config --get CHROME_BINARY           # view a specific value

archivebox config --set CHROME_BINARY=chromium  # persist a config using CLI
# OR
echo CHROME_BINARY=chromium >> ArchiveBox.conf  # persist a config using file
# OR
env CHROME_BINARY=chromium archivebox ...       # run with a one-off config

These methods also work the same way when run inside Docker, see the Docker Configuration wiki page for details.

The config loading logic with all the options defined is here: archivebox/

Most options are also documented on the Configuration Wiki page.

Most Common Options to Tweak

# e.g. archivebox config --set TIMEOUT=120

TIMEOUT=120                # default: 60    add more seconds on slower networks
CHECK_SSL_VALIDITY=True    # default: False True = allow saving URLs w/ bad SSL
SAVE_ARCHIVE_DOT_ORG=False # default: True  False = disable saving
MAX_MEDIA_SIZE=1500m       # default: 750m  raise/lower youtubedl output size

PUBLIC_INDEX=True          # default: True  whether anon users can view index
PUBLIC_SNAPSHOTS=True      # default: True  whether anon users can view pages
PUBLIC_ADD_VIEW=False      # default: False whether anon users can add new URLs


For better security, easier updating, and to avoid polluting your host system with extra dependencies, it is strongly recommended to use the official Docker image with everything pre-installed for the best experience.

To achieve high-fidelity archives in as many situations as possible, ArchiveBox depends on a variety of 3rd-party tools and libraries that specialize in extracting different types of content. These optional dependencies used for archiving sites include:

You don’t need to install every dependency to use ArchiveBox. ArchiveBox will automatically disable extractors that rely on dependencies that aren’t installed, based on what is configured and available in your $PATH.

If not using Docker, make sure to keep the dependencies up-to-date yourself and check that ArchiveBox isn’t reporting any incompatibility with the versions you install.

# install python3 and archivebox with your system package manager
# apt/brew/pip/etc install ... (see Quickstart instructions above)

archivebox setup       # auto install all the extractors and extras
archivebox --version   # see info and check validity of installed dependencies

Installing directly on Windows without Docker or WSL/WSL2/Cygwin is not officially supported (I cannot respond to Windows support tickets), but some advanced users have reported getting it working.

For detailed information about upgrading ArchiveBox and its dependencies, see:

Archive Layout

All of ArchiveBox’s state (including the index, snapshot data, and config file) is stored in a single folder called the “ArchiveBox data folder”. All archivebox CLI commands must be run from inside this folder, and you first create it by running archivebox init.

The on-disk layout is optimized to be easy to browse by hand and durable long-term. The main index is a standard index.sqlite3 database in the root of the data folder (it can also be exported as static JSON/HTML), and the archive snapshots are organized by date-added timestamp in the ./archive/ subfolder.


Each snapshot subfolder ./archive/<timestamp>/ includes a static index.json and index.html describing its contents, and the snapshot extractor outputs are plain files within the folder.

Static Archive Exporting

You can export the main index to browse it statically without needing to run a server.

Note These exports are not paginated, exporting many URLs or the entire archive at once may be slow. Use the filtering CLI flags on the archivebox list command to export specific Snapshots or ranges.

# archivebox list --help
archivebox list --html --with-headers > index.html     # export to static html table
archivebox list --json --with-headers > index.json     # export to json blob
archivebox list --csv=timestamp,url,title > index.csv  # export to csv spreadsheet

# (if using Docker Compose, add the -T flag when piping)
# docker compose run -T archivebox list --html --filter-type=search snozzberries > index.json

The paths in the static exports are relative, make sure to keep them next to your ./archive folder when backing them up or viewing them.

security graphic


Archiving Private Content

If you’re importing pages with private content or URLs containing secret tokens you don’t want public (e.g Google Docs, paywalled content, unlisted videos, etc.), you may want to disable some of the extractor methods to avoid leaking that content to 3rd party APIs or the public.

# don't save private content to ArchiveBox, e.g.:
archivebox add ''
archivebox add ''

# without first disabling saving to
archivebox config --set SAVE_ARCHIVE_DOT_ORG=False  # disable saving all URLs in

# restrict the main index, Snapshot content, and Add Page to authenticated users as-needed:
archivebox config --set PUBLIC_INDEX=False
archivebox config --set PUBLIC_SNAPSHOTS=False
archivebox config --set PUBLIC_ADD_VIEW=False 

# if extra paranoid or anti-Google:
archivebox config --set SAVE_FAVICON=False          # disable favicon fetching (it calls a Google API passing the URL's domain part only)
archivebox config --set CHROME_BINARY=chromium      # ensure it's using Chromium instead of Chrome

Security Risks of Viewing Archived JS

Be aware that malicious archived JS can access the contents of other pages in your archive when viewed. Because the Web UI serves all viewed snapshots from a single domain, they share a request context and typical CSRF/CORS/XSS/CSP protections do not work to prevent cross-site request attacks. See the Security Overview page and Issue #239 for more details.

# visiting an archived page with malicious JS:

# can now make a request to read everything from:*
# then can send it off to some evil server

The admin UI is also served from the same origin as replayed JS, so malicious pages could also potentially use your ArchiveBox login cookies to perform admin actions (e.g. adding/removing links, running extractors, etc.). We are planning to fix this security shortcoming in a future version by using separate ports/origins to serve the Admin UI and archived content (see Issue #239).

Note: Only the wget & dom extractor methods execute archived JS when viewing snapshots, all other archive methods produce static output that does not execute JS on viewing. If you are worried about these issues ^ you should disable these extractors using archivebox config --set SAVE_WGET=False SAVE_DOM=False.

Saving Multiple Snapshots of a Single URL

First-class support for saving multiple snapshots of each site over time will be added eventually (along with the ability to view diffs of the changes between runs). For now ArchiveBox is designed to only archive each unique URL with each extractor type once. The workaround to take multiple snapshots of the same URL is to make them slightly different by adding a hash:

archivebox add ''
archivebox add ''

The Re-Snapshot Button button in the Admin UI is a shortcut for this hash-date workaround.

Storage Requirements

Because ArchiveBox is designed to ingest a firehose of browser history and bookmark feeds to a local disk, it can be much more disk-space intensive than a centralized service like the Internet Archive or ArchiveBox can use anywhere from ~1gb per 1000 articles, to ~50gb per 1000 articles, mostly dependent on whether you’re saving audio & video using SAVE_MEDIA=True and whether you lower MEDIA_MAX_SIZE=750mb.

Disk usage can be reduced by using a compressed/deduplicated filesystem like ZFS/BTRFS, or by turning off extractors methods you don’t need. You can also deduplicate content with a tool like fdupes or rdfind. Don’t store large collections on older filesystems like EXT3/FAT as they may not be able to handle more than 50k directory entries in the archive/ folder. Try to keep the index.sqlite3 file on local drive (not a network mount) or SSD for maximum performance, however the archive/ folder can be on a network mount or slower HDD.


brew install archivebox
archivebox version
archivebox init
archivebox add archivebox data dir
archivebox server archivebox server add archivebox server list archivebox server detail

paisley graphic

Background & Motivation

ArchiveBox aims to enable more of the internet to be saved from deterioration by empowering people to self-host their own archives. The intent is for all the web content you care about to be viewable with common software in 50 - 100 years without needing to run ArchiveBox or other specialized software to replay it.

Vast treasure troves of knowledge are lost every day on the internet to link rot. As a society, we have an imperative to preserve some important parts of that treasure, just like we preserve our books, paintings, and music in physical libraries long after the originals go out of print or fade into obscurity.

Whether it’s to resist censorship by saving articles before they get taken down or edited, or just to save a collection of early 2010’s flash games you love to play, having the tools to archive internet content enables to you save the stuff you care most about before it disappears.

Image from WTF is Link Rot?...

The balance between the permanence and ephemeral nature of content on the internet is part of what makes it beautiful. I don’t think everything should be preserved in an automated fashion–making all content permanent and never removable, but I do think people should be able to decide for themselves and effectively archive specific content that they care about.

Because modern websites are complicated and often rely on dynamic content, ArchiveBox archives the sites in several different formats beyond what public archiving services like save. Using multiple methods and the market-dominant browser to execute JS ensures we can save even the most complex, finicky websites in at least a few high-quality, long-term data formats.

Comparison to Other Projects


Check out our community page for an index of web archiving initiatives and projects.

A variety of open and closed-source archiving projects exist, but few provide a nice UI and CLI to manage a large, high-fidelity archive collection over time.

ArchiveBox tries to be a robust, set-and-forget archiving solution suitable for archiving RSS feeds, bookmarks, or your entire browsing history (beware, it may be too big to store), including private/authenticated content that you wouldn’t otherwise share with a centralized service (this is not recommended due to JS replay security concerns).

Comparison With Centralized Public Archives

Not all content is suitable to be archived in a centralized collection, whether because it’s private, copyrighted, too large, or too complex. ArchiveBox hopes to fill that gap.

By having each user store their own content locally, we can save much larger portions of everyone’s browsing history than a shared centralized service would be able to handle. The eventual goal is to work towards federated archiving where users can share portions of their collections with each other.

Comparison With Other Self-Hosted Archiving Options

ArchiveBox differentiates itself from similar self-hosted projects by providing both a comprehensive CLI interface for managing your archive, a Web UI that can be used either independently or together with the CLI, and a simple on-disk data format that can be used without either.

ArchiveBox is neither the highest fidelity nor the simplest tool available for self-hosted archiving, rather it’s a jack-of-all-trades that tries to do most things well by default. It can be as simple or advanced as you want, and is designed to do everything out-of-the-box but be tuned to suit your needs.

If you want better fidelity for very complex interactive pages with heavy JS/streams/API requests, check out and

If you want more bookmark categorization and note-taking features, check out Archivy, Memex, Polar, or LinkAce.

If you need more advanced recursive spider/crawling ability beyond --depth=1, check out Browsertrix, Photon, or Scrapy and pipe the outputted URLs into ArchiveBox.

For more alternatives, see our list here

dependencies graphic

Internet Archiving Ecosystem

Whether you want to learn which organizations are the big players in the web archiving space, want to find a specific open-source tool for your web archiving need, or just want to see where archivists hang out online, our Community Wiki page serves as an index of the broader web archiving community. Check it out to learn about some of the coolest web archiving projects and communities on the web!

Need help building a custom archiving solution?

Hire the team that built Archivebox to work on your project. (@ArchiveBoxApp)

(We also offer general software consulting across many industries)

documentation graphic


We use the GitHub wiki system and Read the Docs (WIP) for documentation.

You can also access the docs locally by looking in the ArchiveBox/docs/ folder.

Getting Started


More Info


ArchiveBox Development

All contributions to ArchiveBox are welcomed! Check our issues and Roadmap for things to work on, and please open an issue to discuss your proposed implementation before working on things! Otherwise we may have to close your PR if it doesn’t align with our roadmap.

For low hanging fruit / easy first tickets, see: ArchiveBox/Issues #good first ticket #help wanted.

Python API Documentation:

Setup the dev environment

Click to expand... #### 1. Clone the main code repo (making sure to pull the submodules as well) ```bash git clone --recurse-submodules cd ArchiveBox git checkout dev # or the branch you want to test git submodule update --init --recursive git pull --recurse-submodules ``` #### 2. Option A: Install the Python, JS, and system dependencies directly on your machine ```bash # Install ArchiveBox + python dependencies python3 -m venv .venv && source .venv/bin/activate && pip install -e '.[dev]' # or: pipenv install --dev && pipenv shell # Install node dependencies npm install # or archivebox setup # Check to see if anything is missing archivebox --version # install any missing dependencies manually, or use the helper script: ./bin/ ``` #### 2. Option B: Build the docker container and use that for development instead ```bash # Optional: develop via docker by mounting the code dir into the container # if you edit e.g. ./archivebox/core/ on the docker host, runserver # inside the container will reload and pick up your changes docker build . -t archivebox docker run -it \ -v $PWD/data:/data \ archivebox init --setup docker run -it -p 8000:8000 \ -v $PWD/data:/data \ -v $PWD/archivebox:/app/archivebox \ archivebox server --debug --reload # (remove the --reload flag and add the --nothreading flag when profiling with the django debug toolbar) # When using --reload, make sure any files you create can be read by the user in the Docker container, eg with 'chmod a+rX'. ```

Common development tasks

See the ./bin/ folder and read the source of the bash scripts within. You can also run all these in Docker. For more examples see the GitHub Actions CI/CD tests that are run: .github/workflows/*.yaml.

Run in DEBUG mode

Click to expand... ```bash archivebox config --set DEBUG=True # or archivebox server --debug ... ```

Install and run a specific GitHub branch

Click to expand... ```bash # docker-compose.yml: services: archivebox: image: archivebox/archivebox:dev build: '' ... # docker: docker build -t archivebox:dev docker run -it -v $PWD:/data archivebox:dev init --setup # bare metal: pip install 'git+' npm install 'git+' archivebox init --setup ```

Run the linters

Click to expand... ```bash ./bin/ ``` (uses `flake8` and `mypy`)

Run the integration tests

Click to expand... ```bash ./bin/ ``` (uses `pytest -s`)

Make migrations or enter a django shell

Click to expand... Make sure to run this whenever you change things in ``. ```bash cd archivebox/ ./ makemigrations cd path/to/test/data/ archivebox shell archivebox manage dbshell ``` (uses `pytest -s`)

Contributing a new extractor

Click to expand...

ArchiveBox [`extractors`]( are external binaries or Python/Node scripts that ArchiveBox runs to archive content on a page. Extractors take the URL of a page to archive, write their output to the filesystem `archive///...`, and return an [`ArchiveResult`](,class%20ArchiveResult,-(models.Model)%3A) entry which is saved to the database (visible on the `Log` page in the UI). *Check out how we added **[`archivebox/extractors/`](** as an example of the process: [Issue #399]( + [PR #403](*
**The process to contribute a new extractor is like this:** 1. [Open an issue]( with your propsoed implementation (please link to the pages of any new external dependencies you plan on using) 2. Ensure any dependencies needed are easily installable via a package managers like `apt`, `brew`, `pip3`, `npm` (Ideally, prefer to use external programs available via `pip3` or `npm`, however we do support using any binary installable via package manager that exposes a CLI/Python API and writes output to stdout or the filesystem.) 3. Create a new file in [`archivebox/extractors/.py`]( (copy an existing extractor like [``]( as a template) 4. Add config settings to enable/disable any new dependencies and the extractor as a whole, e.g. `USE_DEPENDENCYNAME`, `SAVE_EXTRACTORNAME`, `EXTRACTORNAME_SOMEOTHEROPTION` in [`archivebox/`]( 5. Add a preview section to [`archivebox/templates/core/snapshot.html`]( to view the output, and a column to [`archivebox/templates/core/index_row.html`]( with an icon for your extractor 6. Add an integration test for your extractor in [`tests/`]( 7. [Submit your PR for review!]( 🎉 8. Once merged, please document it in these places and anywhere else you see info about other extractors: - - -

</details> #### Build the docs, pip package, and docker image
Click to expand... (Normally CI takes care of this, but these scripts can be run to do it manually) ```bash ./bin/ # or individually: ./bin/ ./bin/ ./bin/ ./bin/ ./bin/ ```
#### Roll a release
Click to expand... (Normally CI takes care of this, but these scripts can be run to do it manually) ```bash ./bin/ # or individually: ./bin/ ./bin/ ./bin/ ./bin/ ./bin/ ```
--- ## Further Reading - Home: []( - Demo: []( - Docs: []( - Releases: []( - Wiki: []( - Issues: []( - Discussions: []( - Community Chat: [Zulip Chat (preferred)]( or [Matrix Chat (old)]( - Social Media: [Twitter](, [LinkedIn](, [YouTube](, [](, [Reddit]( - Donations: []( ---

This project is maintained mostly in my spare time with the help from generous contributors and Monadical Consulting.

Sponsor this project on GitHub

(网站存档 / 爬虫)

✨ Have spare CPU/disk/bandwidth and want to help the world?
Check out our Good Karma Kit...