Artifact identity
A unique Artifact ID helps distinguish one capture from another and provides a stable filename foundation.
A capture is more than a screenshot. BrowserBeast creates structured local records designed for preservation, review, research, and AI workflows.
An Evidence File combines the readable capture with the context needed to understand where the record came from and how it was created.
A unique Artifact ID helps distinguish one capture from another and provides a stable filename foundation.
The originating URL and page title remain attached to the record instead of living in a separate bookmark.
Timestamp, mode, browser, platform, word count, and tool version explain how the file was made.
Advisory privacy indicators tell you when a capture deserves extra attention before sharing.
| Capability | Ordinary screenshot | BrowserBeast Evidence File |
|---|---|---|
| Visual appearance | Strong | Not its primary purpose |
| Searchable readable text | Usually no | Yes |
| Source URL and timestamp | Not inherently | Included |
| Structured AI-ready content | No | Markdown and plain text |
| Capture provenance | Limited | Evidence Envelope metadata |
| Human review workflow | Visual inspection | Preview plus local Full Review |
Screenshots remain valuable for visual proof. Evidence Files serve a different purpose: preserving readable content and practical provenance.
The Evidence Envelope is a structured metadata block embedded alongside the capture. It helps software—and future you—identify the artifact, the capture tool, the source, and relevant review signals.
It is evidence-ready documentation, not a cryptographic signature or legal certification.
```evidence-envelope
evidence_envelope_version: "0.2"
artifact:
artifact_id: "bb-20260716-162157-ztz4og"
artifact_type: "browser_capture"
created_by_tool: "BrowserBeast"
source_url: "https://example.com/"
capture:
mode: "full_render"
review_before_sharing: true
```Choose Full Render or Highlighted Text. BrowserBeast reads the content only after you trigger the action.
Inspect the capture summary, metadata, content preview, and any advisory privacy warning.
Copy Markdown, download an `.md` file, copy plain text, or open the local Full Review.
BrowserBeast does not require an AI Underground account, does not capture in the background, and does not upload your Evidence Files to an AI Underground cloud service.
Your browser and normal download settings determine where downloaded files go. You decide what gets copied, stored, shared, or deleted.
Evidence Files can preserve private conversations, account context, visible identifiers, or confidential material. Privacy signals are advisory; they do not redact content and cannot guarantee that a capture is safe to publish.