ArchiveBox

ArchiveBox/ArchiveBox

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

Ship status

Still shipping

Pushed in the last 30 days.

Last push
Oct 16, 2026
today
Ship score
100/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 28,211 → 28,743 (Sep 1 – Oct 13, 2026)
+310 stars in the 28 days to 2026-10-13

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repo facts

What GitHub reports.

Stars
28.8K
Forks
1.6K
Open issues
155
Watchers
187
Primary language
Python
Created
May 5, 2017
Owner
ArchiveBox · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. OSI-approved license — GitHub’s own license field, not legal advice. 111 startups in the directory ship primarily in Python.

Topics

#archivebox#backups#bookmark-archiver#browser-bookmarks#chromium#digipres#firefox#headless-browser#internet-archiving#pinboard#pocket#python#rss#self-hosted#singlefile#warc#wayback-machine#web-archiving#wget#youtube-dl

How it got here

What the classifier decided, and when.

Classified as an open-source startup by Jev, TypeSafe’s classifier, on Sep 22, 2026 — os_startup 53%, self-hostable 98%, hosted offering 33%. The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory.

Listed since the 2025-09 crawl. Answered by jev-1.13.0. How the classification works →

Embed your status

Put this badge on your README.

OSSEAN ship status: shipping — last push 2026-10-16This is the badge for ArchiveBox/ArchiveBox, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/ArchiveBox/ArchiveBox.svg)](https://ossean.com/ArchiveBox/ArchiveBox)

Updates daily, from the last push GitHub saw.

Honest caveat: GitHub proxies README images through Camo and rewrites the anchor with rel=“nofollow”, so a README embed sends you referral traffic and brand, not link equity. The link is dofollow wherever you control the markup — your docs, your landing page, your blog. The snippet uses your frozen OSSEAN slug, so it survives a repo rename.