LocalKeepFlash · open source · local-first

Save the web to your own folder.

LocalKeepFlash saves web pages, selected passages, images, and YouTube transcripts as Markdown and local assets. Choose a folder and keep using the tools you already know.

  • AGPL-3.0
  • No account or telemetry
  • Chromium extension
Current browser tab

The exact source you chose

Capture locally

Your research folder

  • source-note.md
  • cover.webp
No cloud hop

Four capture modes

Pages, passages, images, and transcripts.

Each capture retains useful context and produces files that can move into the tools you already use.

Readable webpages

Convert headings, links, lists, tables, quotes, and code into clean Markdown while keeping the source URL.

Output · Markdown + assets

Exact selections

Save only the passage that mattered, with canonical and text-fragment links when the page supports them.

Output · quote + source

Images with context

Download a raster image beside a searchable Markdown note instead of leaving only a fragile remote URL.

Output · image + note

YouTube transcripts

Keep metadata, cover art, chapters, and timestamped captions as a research-ready Markdown file.

Output · timed transcript

A three-step workflow

Choose a folder. Start collecting.

  1. 01

    Choose your folder

    Select the directory that will hold notes and assets, plus preferred caption languages.

  2. 02

    Capture from the source

    Open the extension on the current page, selection, image, or YouTube video when you decide to save.

  3. 03

    Continue in your tools

    Use the files in Obsidian, a code editor, Git, search tools, or another Markdown workflow.

A deliberately short data path

Files first. Service optional.

LocalKeepFlash is built around a simple boundary: the extension extracts what you ask for and writes it to a directory you selected.

What you keep

  • Readable Markdown with source metadata
  • Raster images and YouTube cover art
  • A visible, versioned folder structure

What is not required

  • No KeepFlash account or API
  • No cloud database, analytics, or AI
  • No proprietary archive to export later

Install the extension

Start in the Chrome Web Store.

Install the extension, choose a destination folder, and save from the page you are reading. Developers can also build it from the source on GitHub.

Add to Chrome

Current release: 0.1.1. PDF viewers, file:// URLs, browser-internal pages, and Incognito mode are not supported.

Build from source (developers)
  • Node.js 22 or later
  • npm
  • Chrome or Microsoft Edge 122 or later

Build the unpacked extension

git clone https://github.com/dante-is-shipping/LocalKeepFlash.git
cd LocalKeepFlash
npm install
npm run dev
Read the complete installation guide

LocalKeepFlash and KeepFlash

Local files or a connected workspace.

The two products solve different parts of the knowledge workflow and remain useful independently.

LocalKeepFlash

Use it when direct file ownership, a transparent saving path, and Markdown compatibility are the destination.

KeepFlash

Use the hosted workspace when you need cross-source search, connections, annotations, and AI with the original context visible.

Try KeepFlash free

LocalKeepFlash does not automatically sync captures to KeepFlash. A KeepFlash account is never required to save local files.

Explore by workflow

Start with the source you want to keep.

Product questions

LocalKeepFlash FAQ

What is LocalKeepFlash?

LocalKeepFlash is a free, open-source, local-first web clipper for Chromium browsers. It saves webpages, selected passages, images, and YouTube transcripts directly to a folder you choose as Markdown and local assets.

Does it require a KeepFlash account?

No. LocalKeepFlash does not use a KeepFlash account or API in its saving path and does not upload captures to KeepFlash.

Can I use the output in Obsidian?

Yes. The output is ordinary Markdown with YAML frontmatter and local asset paths, so it can be opened in Obsidian or another file-based Markdown tool.

Is it available in the Chrome Web Store?

Yes. Select “Add to Chrome” to install it from the Chrome Web Store. The source remains available on GitHub if you prefer to build and load an unpacked extension.

What is the long-term product boundary?

LocalKeepFlash focuses on capture and portable local files. Search, annotations, connections, and AI remain optional downstream workflows rather than requirements in the saving path.

Your sources deserve an exit route

Capture the web without giving up the files.

Inspect the code, build the extension, and keep the result in a format that remains useful beyond one product.

Add to ChromeOpen LocalKeepFlash on GitHubExplore hosted KeepFlash

AGPL-3.0 · public source · contributions welcome