From your first capture to finished work.

Start with one page

1. In Chrome, open an ordinary HTTP or HTTPS page that you are allowed to capture.
2. Open Web2Markdown and choose Single Page. Use Selection when you only want highlighted text.
3. Choose Preview to inspect the Markdown, or Download to save the capture.
4. Check the destination reported by the extension. Open the saved Markdown in your editor.

New users should first check public download availability. The public installer and Store listing are still in preparation.

Choose a capture mode

Single Page

Extracts readable content from the current page. Good for articles, reference pages, and one-off notes.

Selection

Captures the passage you selected before opening the popup.

Site Tree

Follows same-site links with depth and page limits. A deeper limit follows more links, takes longer, and creates more files. Start small and review the result.

Sitemap

Saves available sitemap documents and a URL inventory without opening or converting all the listed pages. Use this when you want the map, not the page content.

Dynamic layouts and protected pages can limit extraction. Preview the result before relying on it as a complete copy.

Keep the capture together

The default destination is Downloads/Web2Markdown. In Settings, Browse can select or create a capture folder on another available drive. Chrome asks for access to the selected folder.

Each receipt-backed capture has its own operation folder. Keep the Markdown, assets folder, and capture.json receipt together so images and capture membership remain intact.

If Chrome cannot access your selected folder, the capture uses Downloads automatically and reports its actual destination. Renew access by choosing the folder again in Settings.

Local image mode saves supported images beside your document. Remote image mode leaves links to the source website, which may change or become unavailable.

Continue in the desktop editor

1. Open your capture from disk or use the desktop Capture Inbox.
2. If you save outside the default capture tree, add the relevant capture root to the Inbox or open the files manually.
3. Edit source alongside the rendered preview. Preview block editing and task toggles update the underlying Markdown.
4. Use tabs or two editor groups to keep related documents open. The tab-management menu includes Close All Tabs; review unsaved-change prompts.

Heading and List controls reuse the last selected style from the main button. Their adjacent arrows choose another style. Select multiple lines before applying a list to the whole selection.

Templates, formats, and exports

Start with the built-in document templates or your local snippet library. Agent instruction files such as AGENTS.md and CLAUDE.md are Markdown; not every Markdown document requires YAML frontmatter. Use the starter appropriate to the intended tool.

Save dotenv files as .env or a named variant such as .env.local. These files may contain secrets: use a safe example when sharing a problem.

Use Save As to choose a text format. Changing a filename suffix is not a semantic conversion between programming languages or configuration formats. For a finished document, use export to produce plain text, PDF, or DOCX and inspect the output.

Document Check offers format-aware findings and some previewable fixes. Check depth varies by format; it does not replace the target system's own validation.

Preview, recovery, and safe changes

The popup and persistent side panel share a source-bound draft. If another panel changes it, resolve the conflict before saving. Draft recovery is bounded local storage, not a backup. Use Clear draft when a retained capture contains sensitive material.

Interrupted Site Tree jobs do not resume by themselves. Use the available Resume, Retry failed, or Save partial action after reviewing the retained job.

For folder replacement or metadata batches in the desktop editor, review the proposed changes and selected files before applying. Keep independent backups of important work.

Optional evidence and agent access

Page SEO evidence saves bounded rendered-page facts beside the Markdown. Sitemap viewing compares local information without visiting every listed URL. Neither feature proves indexing, search ranking, HTTP status, or page performance.

Agent connection is optional. Only enable it for a local agent you intend to trust. Page capture controls can be hidden from extension Settings when they interfere with browsing.

The packaged native bridge requires separate local setup. A successful connection alone does not prove delivery: verify the matching test capture in the desktop Inbox. Mac bridge compatibility is not yet claimed.

Find the next answer

Both components include local Help and About. Settings fields offer explanations through their help controls. Use the in-app Help Center for the detailed reference matching your installed build.

Troubleshoot capture and editor issues, review privacy and local storage, or check release preparation.