🧅 Dark Web Scroll · Pro plan and up

Turn a .onion page into a scroll video, safely

Dark Web Scroll captures a Tor (.onion) page the same way Scrollify captures any public site — one continuous scroll, rendered to MP4, GIF, or WebM — for threat intelligence, OSINT, brand-protection, and compliance teams who need a shareable visual record without opening Tor Browser themselves.

Requires a Pro plan or higher and a one-time legal acknowledgement. See acceptable use below.

Without a capture process
  • An analyst opens Tor Browser, screenshots a forum thread, and the below-the-fold context is gone
  • A leak site or marketplace listing changes or disappears before it can be reported internally
  • Sharing a raw .onion link in a report means every reader needs Tor configured to verify it
  • No consistent, dated record of what a hidden-service page actually showed
With Dark Web Scroll
  • One continuous scroll of the full page — nothing cropped, no manual screenshotting
  • A standard MP4/GIF/WebM file that opens on any device, no Tor Browser required to view it
  • Every request routed over Tor with a fresh circuit, isolated from your normal capture traffic
  • Every attempt — successful or blocked — is logged with a timestamp for your own audit trail

How it works

  1. 1

    Accept the acceptable-use terms

    A one-time acknowledgement, gated to Pro plans and above, confirming the feature is for lawful investigative, compliance, and research use only. Recorded once per account.

  2. 2

    Paste the .onion address

    Scrollify detects a valid Tor v3 hidden-service address automatically and switches the job to route through Tor before capture begins.

  3. 3

    Download or share the scroll

    The finished MP4, GIF, or WebM behaves like any other Scrollify export — private by default, shareable on your terms, never eligible for the public gallery.

Built for lawful investigative work

  • Threat intelligence teams

    Document a leak-site listing or actor forum post for an incident report without asking every reader to open Tor Browser to verify it.

  • Brand & fraud protection

    Capture a marketplace listing selling counterfeit goods or stolen credentials as dated evidence for takedown requests and legal escalation.

  • Journalists & researchers

    Preserve how a hidden-service page looked at the time of reporting, with a standard video file that fits directly into a newsroom's normal editorial workflow.

  • Corporate compliance & legal

    Add a Dark Web Scroll capture alongside other exhibits when a breach-notification or vendor-risk file needs to show what a page displayed, and when.

  • Security researchers

    Log a fresh, timestamped capture of a public hidden service as part of a research writeup, without keeping a personal Tor setup running.

  • Law-enforcement–adjacent teams

    Produce a shareable video artifact for a case file or partner briefing where a screenshot alone would miss page context below the fold.

Frequently asked questions

What plan do I need?
Dark Web Scroll is available on the Pro plan and above. Free and Starter plans can capture ordinary public (clearnet) URLs, but a .onion address requires Pro-level entitlement plus the one-time acceptable-use acknowledgement.
Do I need Tor Browser installed?
No. Scrollify routes the capture request through Tor on its own infrastructure — you paste the .onion address and download a standard MP4, GIF, or WebM file that plays anywhere, with no Tor client needed on your end.
What addresses are supported?
Current Tor v3 (.onion) hidden-service addresses. Legacy v2 addresses (16-character) were deprecated across the Tor network and are not supported.
Can these captures show up in the public gallery?
No — .onion captures can never be approved for the public gallery, regardless of who requests it. Every Dark Web Scroll export is private by default; you choose whether and with whom to share a link.
Is a scroll video a substitute for forensic evidence collection?
No. It produces a clear, repeatable visual record of what a hidden-service page rendered at capture time — a supporting artifact, not a replacement for cryptographic hashing, chain-of-custody tooling, or certified forensic collection. Treat it as one layer in a preservation strategy your team defines.
What happens if I try without accepting the terms, or on an ineligible plan?
The request is blocked before any capture begins, and the attempt is still logged for audit purposes. Accepting the acceptable-use terms and holding a Pro-or-higher plan are both required before a .onion job can run.

More on evidence & compliance capture

Capture it once, share it as a video

Pro plans and up. Legal acknowledgement required before the first .onion capture.

Start on Pro See what's included in every plan →