SwiftShot · court-ready evidence capture
Hash every screenshot the moment you take it, annotate without touching the original, and hand opposing counsel a verification trail instead of a PNG that might have been edited.
35-second tour
Narrated walkthrough recorded from the real app.
The problem
A screenshot saved to a case folder looks like evidence. Then someone asks whether it could have changed since it was taken, and a plain image file has no way to answer.
How it works
One click: visible area, a region, or the full page, with sticky headers handled.
SHA-256 is computed the moment you capture. Change one pixel and it no longer matches.
Highlights, arrows, redactions, and Bates stamps land on a copy. The original and its hash stay untouched, and every edit is logged.
One click to WORM storage (Pro), or a PDF package with the hash, URL, timestamp, and custody log.
"We never received the tenant's notice. The deposit is forfeited."
AIBridges
················································Tamper test
This is the check behind every SwiftShot capture. Edit the sample exhibit below: even a single space gives it a completely different fingerprint.
computing…
computing…
Computed in your browser with the standard SHA-256 function. Nothing you type is sent anywhere.
The difference
ade7…f8ebmatch4 eventsSee the editor
Each clip is recorded from the SwiftShot editor on demonstration material. No client or case data.
Features
Every capture is cryptographically fingerprinted at the moment of the click. Change one pixel and the fingerprint no longer matches.
Visible area, region select, or full-page scroll, with automatic sticky-header handling so long pages stitch cleanly.
Arrows, rectangles, text, and highlights with full color control. All edits logged.
Black box, blur, or pixelate. Permanently destroys the pixel data underneath.
Exhibit labels, CONFIDENTIAL, and auto-incrementing Bates numbers in one click.
OCR a captured page and review dense legal text in a focused reader before marking the clauses that matter.
Tamper-proof AWS storage with governance retention and per-case retention periods, plus a chain-of-custody log.
Claude Code + SwiftShot CLI
SwiftShot ships with a command-line tool. It pulls the text out of a capture with OCR and pipes it straight into Claude Code: parties, dates, risk flags, and deposition angles in seconds, not hours.
Parties, dates, obligations, and unusual clauses, formatted for case notes.
Ranked follow-up questions and contradictions with prior statements.
A dated event list with citations back to each exhibit.
Weak arguments and unsupported assertions, with counterpoints.
# Capture a contract page and analyze it$ swiftshot-cli evidence extract exhibit_A.png --ocr --json \ | claude -p "You are a litigation paralegal. Identify all parties, key dates, obligations, and any clauses that could be challenged at trial." Claude:Parties: Harbor Point Lending LLC (Lender) · Anderson, James R. (Borrower)Execution date: March 4, 2021 (3 days before disclosure deadline)⚠ Section 4.2: ARM adjustment cap absent, potential TILA violation⚠ Section 7: arbitration clause uses "shall", may be mandatory in RIDepo angle: ask lender rep when Section 4.2 language was finalized
Works with Claude Code and any AI tool that accepts piped text. OCR runs on your machine; nothing leaves it unless you choose Cloud Vault.
Time savings
By hand, one capture means screenshot, save, rename, log it in a spreadsheet, email it, and check the URL. Set your own numbers.
Estimate from your inputs. SwiftShot time is counted as 30 seconds per capture: click, annotate, preserve.
Pricing
All plans process locally. Your data never touches our servers unless you opt into Cloud Vault.
Firm setup
AIBridges configures capture rules, custody workflows, training, and storage so SwiftShot fits how your team actually handles evidence.
Make every capture answer the authenticity question before anyone asks it. Installs in about ten seconds.