Skip to content

link-assistant/web-capture

Repository files navigation

web-capture

JavaScript: npm version npm downloads CI - JavaScript

Rust: crates.io version crates.io downloads docs.rs CI - Rust

Release: GitHub Release License: Unlicense

A CLI and microservice to fetch URLs and render them as:

  • Markdown: Clean HTML-to-Markdown conversion with image extraction
  • HTML: Rendered page content
  • Plain text: Raw text downloads for paste-like URLs such as xpaste.pro
  • PNG/JPEG screenshot: Viewport or full-page capture
  • ZIP archive: Markdown/HTML + locally downloaded images
  • PDF: Print-quality document
  • DOCX: Word document

Language Implementations

This repository contains two implementations with compatible APIs:

Implementation Directory Package Status
JavaScript/Node.js ./js @link-assistant/web-capture Production
Rust ./rust web-capture Production

Both implementations provide the same CLI interface and HTTP API endpoints, allowing you to choose based on your deployment preferences.

Quick Start

JavaScript

cd js
npm install
npm run dev

Rust

cd rust
cargo run -- --serve

API Endpoints

Both implementations expose the same API:

Endpoint Description
GET /html?url=<URL> Get rendered HTML content
GET /txt?url=<URL> Get raw text content, with xpaste.pro paste URLs normalized to /raw
GET /markdown?url=<URL> Get Markdown conversion; xpaste.pro pastes include raw text inline under 1500 lines or as a ZIP when larger
GET /markdown?url=<URL>&converter=kreuzberg High-performance Markdown conversion via html-to-markdown
GET /markdown?url=<URL>&converter=kreuzberg&format=json Structured result with metadata, tables, images, and warnings
GET /image?url=<URL> Get PNG screenshot
GET /archive?url=<URL> Get a ZIP archive with markdown/HTML and images
GET /fetch?url=<URL> Proxy fetch content
GET /stream?url=<URL> Stream content
GET /search?q=<QUERY> Capture structured search-provider results

CLI Usage

# Capture a URL as Markdown (default format, writes to ./data/web-capture/<host>/<path>/)
web-capture https://example.com

# Capture as Markdown and save to specific file
web-capture https://example.com -o page.md

# Write to stdout explicitly
web-capture https://example.com -o -

# Capture as HTML
web-capture https://example.com --format html

# Capture raw paste text
web-capture https://xpaste.pro/p/t4q0Lsp0 --format txt -o paste.txt

# Take a screenshot
web-capture https://example.com --format png -o screenshot.png

# Create a ZIP archive
web-capture https://example.com --archive

# Start as API server
web-capture --serve

# Start server on custom port
web-capture --serve --port 8080

CLI Options

Option Short Description Default
--serve -s Start as HTTP API server -
--port -p Port to listen on 3000
--format -f Output format: markdown/md, html, txt/text, image/png, jpeg, pdf, docx, archive markdown
--output -o Output file path. Use -o - for stdout auto-derived from URL
--data-dir Base directory for auto-derived output paths ./data/web-capture
--engine -e Browser engine (JS only): puppeteer, playwright puppeteer
--embed-images Keep images inline as base64 data URIs (self-contained file) false
--no-extract-images Alias for --embed-images false
--extract-images[=DIR] Extract images to DIR/images/ (or next to the output) and download remote images -
--keep-original-links Keep remote image URLs as direct links (the default markdown behavior) false
--images-dir Subdirectory name for extracted images images
--archive Create archive: zip (default), 7z, tar.gz, tar -
--extract-latex Extract LaTeX formulas true
--extract-metadata Extract article metadata true
--post-process Apply post-processing true
--detect-code-language Detect code block languages true

Image Handling

Markdown output supports three image modes, and every capture path (browser or API, CLI or server) routes through the same chokepoint so a flag behaves identically regardless of how the page was captured:

Mode Flag Result
Direct links (default) none / --keep-original-links Remote images stay as direct https://… URLs. Inline base64 (which has no remote URL to restore) is stripped to a placeholder with a warning — never silently kept as a multi-megabyte blob. No images/ folder.
Embed --embed-images Base64 images are kept inline, producing a single self-contained file.
Extract --extract-images[=DIR] Inline base64 and remote images are written to DIR/images/ (defaults to next to the output file) and the markdown is rewritten to reference the local files.

The --archive formats always bundle images into the archive's images/ folder regardless of these flags.

Environment Variables

All flags can be controlled via environment variables:

Variable Description Default
WEB_CAPTURE_DATA_DIR Base directory for output ./data/web-capture
WEB_CAPTURE_EMBED_IMAGES 0/1 — keep images inline 0
WEB_CAPTURE_EXTRACT_IMAGES Directory to extract images into -
WEB_CAPTURE_KEEP_ORIGINAL_LINKS 0/1 — keep original remote URLs 0
WEB_CAPTURE_IMAGES_DIR Subdirectory for extracted images images
WEB_CAPTURE_EXTRACT_LATEX 0/1 — extract LaTeX 1
WEB_CAPTURE_EXTRACT_METADATA 0/1 — extract metadata 1
WEB_CAPTURE_POST_PROCESS 0/1 — post-processing 1
WEB_CAPTURE_DETECT_CODE_LANGUAGE 0/1 — detect code langs 1

API Endpoints

Both implementations expose the same API:

Endpoint Description
GET /html?url=<URL> Get rendered HTML content
GET /txt?url=<URL> Get raw text content, including normalized xpaste.pro raw paste text
GET /markdown?url=<URL> Get Markdown; xpaste.pro pastes include raw text inline under 1500 lines or as a ZIP when larger
GET /markdown?url=<URL>&converter=kreuzberg Get Markdown with the high-performance converter
GET /markdown?url=<URL>&converter=kreuzberg&format=json Get structured Markdown conversion data
GET /markdown?url=<URL>&embedImages=true Get Markdown with base64 images inline
GET /markdown?url=<URL>&keepOriginalLinks=false Get Markdown with all images stripped
GET /image?url=<URL> Get PNG screenshot
GET /archive?url=<URL> ZIP archive with markdown + images extracted to images/
GET /archive?url=<URL>&keepOriginalLinks=true ZIP archive keeping original remote image URLs
GET /archive?url=<URL>&embedImages=true ZIP archive with base64 images inline
GET /pdf?url=<URL> PDF with embedded images
GET /docx?url=<URL> DOCX with embedded images
GET /fetch?url=<URL> Proxy fetch content
GET /stream?url=<URL> Stream content

Docker

JavaScript

cd js
docker build -t web-capture-js .
docker run -p 3000:3000 web-capture-js

Rust

cd rust
docker build -t web-capture-rust .
docker run -p 3000:3000 web-capture-rust

Project Structure

web-capture/
├── js/                          # JavaScript/Node.js implementation
│   ├── src/                     # Source code
│   ├── bin/                     # CLI entry point
│   ├── tests/                   # Test files
│   ├── examples/                # Usage examples
│   ├── package.json             # npm package manifest
│   ├── Dockerfile               # Docker build file
│   └── README.md                # JavaScript-specific docs
│
├── rust/                        # Rust implementation
│   ├── src/                     # Source code
│   │   ├── lib.rs               # Library exports
│   │   ├── main.rs              # CLI/server entry point
│   │   ├── browser.rs           # Browser automation
│   │   ├── html.rs              # HTML processing
│   │   └── markdown.rs          # Markdown conversion
│   ├── tests/                   # Test files
│   ├── examples/                # Usage examples
│   ├── Cargo.toml               # Cargo package manifest
│   ├── Dockerfile               # Docker build file
│   └── README.md                # Rust-specific docs
│
├── scripts/                     # Shared build/release scripts
│   ├── *.mjs                    # JavaScript-specific scripts
│   ├── xpaste/                  # xpaste fixture capture/regeneration helpers
│   └── rust-*.mjs               # Rust-specific scripts
├── tests/xpaste/data/           # Shared xpaste HTML/text/markdown/screenshot fixtures
│
├── .github/workflows/
│   ├── js.yml                   # JavaScript CI/CD
│   └── rust.yml                 # Rust CI/CD
│
└── README.md                    # This file

Development

JavaScript

cd js
npm install
npm run dev          # Start dev server
npm test             # Run tests
npm run lint         # Run linter

Rust

cd rust
cargo build          # Build
cargo test           # Run tests
cargo clippy         # Run linter
cargo fmt            # Format code

Features

  • Markdown Conversion: Clean HTML-to-Markdown with LaTeX extraction, metadata, and code language detection
  • Plain Text Capture: /txt endpoint and --format txt output for text resources and xpaste.pro raw paste URLs
  • Image Extraction: Base64 data URI images extracted to files with content-hash filenames
  • HTML Rendering: Fetch and render HTML with JavaScript support via headless browsers
  • High-Performance Conversion: Optional kreuzberg html-to-markdown backend with structured metadata, table, and image results
  • Screenshots: Capture PNG/JPEG screenshots with theme and viewport control
  • Archives: ZIP archives with markdown/HTML + locally downloaded images
  • Google Docs: Public export, Google Docs REST API, and editor-model capture
  • URL Normalization: Convert relative URLs to absolute
  • Encoding Detection: Automatic charset detection and UTF-8 conversion

Browser Engines

JavaScript Version

  • Puppeteer (default): Mature, well-tested Chrome automation
  • Playwright: Cross-browser automation with similar capabilities

Rust Version

  • browser-commander: A Rust crate for browser automation using chromiumoxide

License

Unlicense — This is free and unencumbered software released into the public domain. You are free to copy, modify, publish, use, compile, sell, or distribute this software for any purpose, commercial or non-commercial, and by any means. See https://unlicense.org for details.

Markdown Converters

web-capture supports three HTML-to-Markdown converter backends across the JavaScript and Rust implementations:

Converter Selection Throughput Structured Results Used In
Turndown (default) converter=turndown ~5-10 MB/s No JS implementation
html2md (default) converter=html2md ~20-40 MB/s No Rust implementation
kreuzberg converter=kreuzberg 150-280 MB/s Yes (metadata, tables, images) Both JS and Rust

The kreuzberg converter is powered by html-to-markdown and uses the same Rust core across both implementations, ensuring consistent output. See integration analysis for details.

Related Projects

  • browser-commander - Browser automation library used in Rust implementation
  • turndown - HTML to Markdown converter used in JS implementation
  • html2md - HTML to Markdown converter used in Rust implementation
  • html-to-markdown - High-performance HTML to Markdown converter (kreuzberg), integrated as optional converter

About

A library, CLI and microservice to capture the web in required format

Resources

License

Stars

Watchers

Forks

Packages

 
 
 

Contributors

Languages