Capture a page or selection, review it, then copy Markdown without building a pack. To combine web captures and local files, keep up to 10 retained sources in the workspace and export one editable context-pack.md.
Install Context Pack with Add to Chrome, then choose the recipe for your source. These steps use the current extension, not an online upload form.
Web page to Markdown
Open the page and let the content you need load. Open Context Pack and choose Capture page. Check the editable Review capture result, then choose Copy Markdown without adding a source or building a pack. For selected text, highlight it first and choose Capture selection. See Quick Copy; use the pack recipe when you want a combined file.
PDF or DOCX to Markdown
Open the extension and choose Open current pack. In the workspace, use Choose files or drag and drop a supported local file. After validation and conversion, it appears in the source list without a browser-capture review panel. Build the pack and inspect the Markdown before exporting. Check PDF and file limits.
Several sources, one .md file
Choose Add to pack after reviewing each browser capture; imported local files go straight into the source list. Keep the workspace open to collect another source. Reorder or exclude sources, then choose Build context pack and inspect the output. Finish with Copy Markdown or Download .md. Up to 10 retained sources share one pack; closing or reloading discards the editable session.
Add your text to the source list, then build and export a combined pack.
Copy a page or selection without building a pack
Link labels that look like Markdown stay readable as literal labels in Preview, not extra nested links. Code and ordinary formatting remain intact; Copy Markdown still exports your unchanged draft.
Choose Capture page or Capture selection. Review and edit Markdown, switch to read-only Preview, then choose Copy Markdown. Copy uses the current draft and leaves review open; nothing is added or built. Add to pack is optional. Cancel discards the pending review without changing earlier sources or output. Direct-PDF review is unchanged.
On a regular webpage, choose Capture table in the popup or workspace. With multiple tables, use Choose a table to select its caption or numbered title; one table opens directly in review. Review Markdown or Preview, then Copy Markdown or Add to pack for one Table source. Switching tables keeps separate edited drafts until Add or Cancel; capture again to refresh the page snapshot.
Already looking at the table you want? Highlight any ordinary text in a cell of that one main-page HTML table, then right-click the highlight and choose Context Pack → Capture selected table. No special word is required; changing a dropdown option is not page-text selection. Review shows the whole sanitized outer table, not just highlighted cells, without a redundant chooser. To keep only the highlighted text, use Capture selected text.
Want to browse tables instead? Open the extension and choose Capture table. Discovery shows its chooser only when multiple tables are found. Review/edit one table, then Copy Markdown or Add to pack. Capture table again returns to discovery.
If capture is unavailable: outside-table or multiple-table selections are rejected with guidance. Select ordinary cell text in just one table and retry. Hidden/editable regions and embedded-frame tables are not captured. If the right-click action is missing inside an embedded frame, open that frame's page in its own tab to retry. Your pending review and existing pack stay unchanged.
Unambiguous merged cells repeat their content with a warning. Complex, nested or headerless tables, and inline code with a backslash immediately before a pipe, fall back to explicit row/cell text when a grid would misrepresent them. Images, including their alt text and image-only links, are omitted from table capture; they are not downloaded. Review Markdown and removal warnings before sharing. Load the rows you need before capture; this action captures loaded HTML tables, not PDF tables or virtualized grids.
Highlight a visible main-frame region for selected links, or clear the selection for visible page links, including navigation/footer links. Choose Extract links in the popup or workspace. Set Text or URL contains, All/Internal/External destinations and Remove duplicate URLs, then Apply filters. Internal means the same protocol, host and port. Replacing an edited draft requires confirmation.
Copy URLs reads the current edited Markdown and exports unique sanitized HTTP/HTTPS destinations in document order, excluding images, code and raw HTML. Copy Markdown exports the draft exactly. Add to pack creates one Links source; Copy, filters and Cancel leave the existing pack unchanged. Extracting links does not open, crawl or fetch their destinations.
Discovery rejects more than 20 eligible tables; direct selected-table capture targets one even when the page contains more. Both enforce DOM/range safety limits and 500,000 combined capture UTF-16 code units. Link extraction rejects more than 1,000 inspected anchors. No silent truncation. Empty or oversized drafts cannot be copied or added. The 10-source and retained-pack limits apply to Add, not standalone Copy.
If Copy or URL parsing fails
For clipboard denial, return to Markdown and select/copy manually. Copy URLs stays disabled while parsing, when no usable URLs remain, or after a bounded-parser failure; edit/retry or use Copy Markdown. See capture troubleshooting.
Review before sharing
Capture is main-frame only and excludes hidden, editable and form-input content. Visible labels and retained link query parameters may still be private: no automatic PII redaction. Preview/filtering/table/link capture make no source requests; the existing direct HTTPS PDF exception is unchanged. Copied text can outlive the workspace in your OS clipboard.
Capture guide
A merged HTML table, captured as Markdown.
The same neutral Regions fixture used in the table screenshot, converted with Context Pack 1.3.0 without editing the Markdown. The numbers are sample data, not product usage figures.
Markdown cannot merge cells. Review warns that merged cells were expanded: repeated values below represent the same original cell, not additional observations.
Regions
| Region | Metric | Value |
| --- | --- | --- |
| Europe | Users | 120 |
| Europe | Teams | 8 |
| Asia | Not published | Not published |
The first run opens Bring several sources into one workspace. Choose Start adding sources or skip the tour. After that, the left column adds and manages sources; the right column holds the built Markdown output.
1
Choose what to captureCapture page, selection, or a supported direct PDF.
2
Review browser capturesEdit local Markdown, then choose Add to pack.
3
Repeat from another tabThe existing workspace is focused and earlier sources stay.
4
Build and exportInspect, copy, or download context-pack.md.
The real two-column workspace after building a pack.
Only the “tour completed” preference is remembered. Use Help in the workspace header to open the tour again. Closing or reloading the workspace discards its editable session.
01 · First browser capture
The popup hands the job to the workspace.
On a regular page, open Context Pack and choose Capture page. The popup closes; Chrome opens or focuses the Context Pack workspace and stages a Review capture panel. Check the title, sanitized URL, warnings, and editable Markdown, then choose Add to pack.
Real extension walkthrough
Choose Capture pageReview capture → Add to pack
1 Open popup2 Capture3 Review and addReady
Popup and review are separate Chrome surfaces.No browser capture joins the pack before review.
Leave the workspace open, move to another page, then capture again from the toolbar, right-click menu, or shortcut. Chrome focuses the existing workspace for review. After Add to pack, the first source remains and the counter becomes 2 included · 2 / 10.
Real extension walkthrough
Same workspace · earlier source retained · 2 / 10
1 Capture tab two2 Review3 Same packReady
One workspace is reused instead of opening duplicates.A busy capture never replaces pending review or conversion.
Files enter through Choose files or drag and drop.
Open the workspace, then choose or drop selectable-text PDF, DOCX, Markdown, or UTF-8 text files. They convert locally and enter the source list after validation. Unlike browser captures, local files do not use the staged Review capture editor.
Real extension walkthrough
Choose files → local conversion → source list
1 Choose or drop2 Convert locally3 Sources retainedReady
No local file path is shown in the pack.Use selectable-text PDFs; OCR is not included.
Simple rectangular DOCX tables keep their rows and columns, including empty cells. Ambiguous merged or uneven rows and richer cells use warned row/cell text. Cell numbers mean source order, not reconstructed visual columns; compare the result with the original document.
Complete headings and lists
Nested DOCX lists retain their hierarchy. A document heading with line breaks becomes one complete heading, with a flattening warning; check it in Sections and Preview. Ordinary paragraph breaks remain breaks.
Review, then export
Read the source warnings and Markdown, choose Build context pack, then inspect Preview. Return to Markdown to edit; Copy Markdown and Download .md export that editable text. Document troubleshooting.
04 · Build and export
The workspace stays two-column from sources to output.
Use the left column to include, exclude, reorder, or remove retained sources. Choose Build context pack; the right column shows editable Markdown and a local token estimate. Choose Preview for a read-only rendered view; return to Markdown to edit. Finish with Copy Markdown or Download .md.
Preview formats your current output locally. Raw HTML remains text and images become alt-text placeholders; no images or remote resources load. Copy Markdown and Download .md always use the editable Markdown, not the rendered view.
Dashboard and table warnings
Supported visible actions, selected non-editable choices, disabled and pressed/expanded states retain meaning. Input values and hidden choices stay excluded. Labels and choice summaries are capped at 200 Unicode code points with a warning when simplified. Complex tables use explicit row/cell text and span annotations when a grid would mislead. This is not a visual replica or automatic PII redaction.
If Preview cannot render
Large or complex output may exceed the bounded renderer. Return to Markdown to edit, copy or download. Changing sources clears stale output; build again before previewing or exporting. Closing or reloading still discards the editable session.
Example output
A real webpage, captured as Markdown.
Our sample page becomes one source in context-pack.md, keeping its headings, numbered list and table. Add other pages or supported files to the same workspace to build a combined pack.
Captured with Context Pack 1.2.0 and built without editing the Markdown. This is one reproducible webpage example, not a guarantee for every website, PDF or DOCX.
Open the sample page in a new tab. Choose Capture page, review the result, then Add to pack and Build context pack.
The capture review reports that a broader page view was used to retain more structured content. Review that warning before adding. Scroll inside the example to see the complete output.
# Context Pack
## Source S1 — Local Context Pack Field Guide
- Type: Web Page
- URL: <https://tryaiblock.com/tools/context-pack/demo/>
- Sections: A practical guide to local context packs.; Keep sources inspectable; Review before reuse; Match the source to the job
## A practical guide to local context packs.
Bring focused source material together, keep every boundary visible, and inspect the Markdown before it leaves your browser.
---
## Keep sources inspectable
A useful context pack preserves source order and provenance. Start with a small set of relevant documents, remove repeated navigation and visual noise, then review the converted text before combining it.
1. Choose only the sources needed for the task.
2. Review titles, links, warnings, and document boundaries.
3. Build the pack and inspect the complete Markdown.
## Review before reuse
Review each source before combining it. A visible source order makes the final context easier to inspect, edit, and explain before export.
## Match the source to the job
| Source | Useful for |
| --- | --- |
| Readable page | Focused articles and documentation |
| PDF or DOCX | Reference material and working drafts |
| Markdown or text | Notes, briefs, and structured prompts |
Toolbar, right-click, and keyboard actions all stage browser content in the current workspace before it is retained.
Toolbar popup
Capture page reads the current page. Highlight text first to use Capture selection. Open current pack focuses the workspace without capturing.
Right-click
Use Context Pack → Capture this page or, after highlighting text, Capture selected text.
Keyboard
Alt+Shift+M on Windows/Linux or Option+Shift+M on macOS captures the current page. Inspect or change the assigned command at chrome://extensions/shortcuts.
New pack
New pack asks for confirmation when work exists. Closing or reloading always clears the editable session.
PDF and limits
Know the supported boundaries.
The limits keep local conversion and review predictable and prevent partial content from entering a pack.
Direct PDF capture
On an eligible direct HTTPS URL whose path ends in .pdf, the popup changes to Capture PDF. Context Pack makes the requested fetch, validates the response, and parses it locally.
Embedded PDF viewers
Embedded, custom, blob, protected, or plain HTTP PDF viewers are not direct-PDF capture targets. Download the file and add it locally, or open a supported direct HTTPS .pdf URL.
Per-file limits
Markdown/text: 1.5 MB each. PDF/DOCX: 20 MB each and best under 10 MB. PDF: 30 pages per file.
Pack limits
10 retained sources, 50 MB total retained source bytes, 60 PDF pages, and 500,000 generated UTF-16 code units in the final pack.
Not supported
No OCR for scanned/image-only PDFs, encrypted PDF or DOCX, legacy .doc, or malformed non-UTF-8 Markdown/text files.
Failure behavior
A rejected capture or file shows a clear error and does not add partial content or replace sources already retained.
Privacy
Local work after an explicit action.
Context Pack does not passively read tabs and does not require a TryAIBlock account.
Temporary page access
Chrome grants temporary access only after you invoke capture on the current tab.
Local conversion
Page, selection, and file conversion runs in the extension. An eligible direct PDF makes one requested HTTPS fetch from its current URL.
In-memory workspace
The source list and editable output stay in the loaded workspace. Copy or download before closing if you need to keep the result.
Chrome-internal pages such as chrome://version/ cannot be captured. Open a regular HTTP or HTTPS page, invoke Context Pack there, and choose Capture page or Capture selection. If source access expired or its tab closed, return to or reopen that source first. Keep the workspace open: do not reload it or choose New pack to recover capture. See capture error messages and recovery steps.
Why is some webpage content missing from the Markdown?
Capture converts readable content from the current main page; it is not a screenshot or a crawl of linked pages. Hidden or unloaded content, media, and unsupported embedded frames may be omitted. Let the desired section load, capture again, and inspect the warnings before adding. Use Capture selection for a specific visible passage. Do not expect interactive dashboards to retain every visual or control.
Can I convert a scanned PDF or preserve a Word layout exactly?
No OCR is included: PDFs need selectable text. DOCX conversion preserves supported document structure, not page layout; embedded images are omitted and complex or merged tables may lose fidelity. Review the output before use.
Can Context Pack download a protected PDF for me?
No. It does not bypass access or download restrictions. For a custom or embedded viewer, use a supported direct HTTPS PDF URL or add a local copy only when the site allows it. Check capture troubleshooting.
Why did Context Pack return to an existing tab?
That is the intended workspace-reuse flow. It keeps earlier sources together and avoids duplicate Context Pack workspaces.
Why is Capture selection unavailable or empty?
Highlight visible text in the main page first, then invoke Capture selection. Content inside unsupported embedded frames is not part of the main-page selection.
Why can an open PDF still fail?
A browser or site viewer may be a webpage rather than a supported direct HTTPS PDF response. Download the PDF and add it locally when the site allows it.
Where is the working pack saved?
It is not silently persisted. It remains only in the loaded workspace memory until you close or reload it; copy or download the generated Markdown to keep it.