Swioz Story Viewer | View & Download Stories Anonymously
SWIOZ / STORY VIEWER V3.2
READ-ONLY INSTRUMENT
Ephemeral data, permanently structured

SWIOZ STORY VIEWER.

A read-only exploration surface for ephemeral story data. Drop in a handle from any supported network to instantly view active stories, expired frames, highlights, and metrics in one structured, searchable archive. No logins. No footprints. No credentials required.

VIEW STORIESVIEW HIGHLIGHTSEXTRACT FRAMESVIEW METRICSARCHIVE EPHEMERALEXPORT JSON VIEW STORIESVIEW HIGHLIGHTSEXTRACT FRAMESVIEW METRICSARCHIVE EPHEMERALEXPORT JSON

What a story capture looks like.

Each card below is one piece of a story snapshot — an active frame, an expired sequence, a highlight cover, a tagged mention. Hover any card to bring it forward; the viewer organizes them by timeline when you’re ready to work.

STORY
Active story frame capture
morning light, 03·14
EXPIRED
Expired story frame capture
2am, can’t sleep
VIDEO
Story video capture
walk home, 0:15
HIGHLIGHT
Story highlight capture
lisbon, day three
FRAME
Extracted story frame capture
extracted, 04:02
STORY
Active story frame capture
new leaf, finally
STORY
Active story frame capture
show, 11:30pm
EXPIRED
Expired story frame capture
brutalist block
VIDEO
Story video capture
kitchen, 0:08
HIGHLIGHT
Story highlight capture
august, recap
FRAME
Extracted story frame capture
self, in window
STORY
Active story frame capture
group show, may

Nine surfaces. One viewer.

Every layer of a profile’s ephemeral content, broken out into its own inspectable panel — searchable, filterable, and exportable on demand.

01 / 09

Active stories

Browse every currently active story sequence in chronological order. Captions, stickers, timestamps, and exact durations are preserved exactly as they appeared at the moment of capture.

Live · 24h Window · Chronological
02 / 09

Expired stories

Access previously captured story sequences that have passed the 24-hour visibility window. Swioz preserves your historical captures so ephemeral content remains accessible for analysis.

Archived · Diff-Aware · Timestamped
03 / 09

Highlight collections

Open any curated highlight reel as a single contiguous sequence. Cover images, titles, and internal story ordering are preserved and individually addressable.

Covers · Titles · Order
04 / 09

Video story reels

Play back video story content inline with full metadata. View counts, audio references, and exact durations are surfaced alongside the player.

Inline · Metadata · Audio
05 / 09

Frame extraction

Automatically extract individual image frames from video stories. Each frame is content-addressed and linked back to the parent video timestamp.

Stills · Timestamps · Hashing
06 / 09

Engagement metrics

See reaction totals, reply counts, and profile-view triggers associated with stories. Compare side-by-side across any date range or highlight category.

Reactions · Replies · Compare
07 / 09

Mentions & stickers

Surface every account tagged, mentioned, or linked via location and hashtag stickers within a story. A complete cross-section of how the story connects to the wider network.

Tags · Links · Locations
08 / 09

Exit & link tracking

For stories with outbound links, Swioz preserves the destination URL, link sticker text, and swipe-up targets exactly as configured at capture time.

URLs · Referrers · Tracking
09 / 09

Bulk export

Download an entire story sequence as JSON, CSV, or zipped media frames. Structured for downstream analysis in spreadsheets, databases, or BI tools.

JSON · CSV · ZIP

Built like an instrument, not a scraper.

Three core systems do the heavy lifting — a capture engine that respects rate boundaries, a structuring layer that turns raw frames into queryable records, and an export pipeline that hands you back clean data.

A.

Capture engine

Swioz reads only what is already visible. There is no credential handling, no impersonation, no bypassing of access controls — the engine treats the source the same way a browser would, only structured and reproducible.

  • Read-only by design. No write operations, no story replies, no interaction with the source profile.
  • Rate-aware. Requests are throttled and spaced to stay within the source’s own publishing rhythm.
  • Frame-accurate. Video stories are captured frame-by-frame with original durations preserved.
  • Timestamped. Every record carries the exact moment it was observed, not the moment it was published.
capture.logLIVE
IDSOURCESTATUSRATE
#0142story/active200 OK1.2s
#0143story/frame-1200 OK0.9s
#0144story/frame-2200 OK1.4s
#0145story/video-1200 OK0.6s
#0146highlights/all200 OK1.1s
#0147story/meta200 OK1.3s
#0148story/mentions200 OK2.0s
B.

Structuring layer

Raw pages are rewritten into a normalized schema. A story from any supported source looks the same in the viewer — same fields, same datetime format, same duration keys — so cross-source comparison works without further wrangling.

  • Unified schema. Active stories, highlights, and frames share a single typed shape across all sources.
  • Datetime normalization. All timestamps converted to UTC with original timezone preserved as metadata.
  • Media hashing. Every image and video frame is content-addressed, so duplicates across stories are detected automatically.
  • Sticker parsing. Mentions, hashtags, locations, and links are extracted into their own queryable fields.
schema.jsonTYPED
FIELDTYPEEXAMPLEINDEX
iduuida3f…PK
expires_atdatetime2025-03-15IDX
durationint (ms)15000
media_typeenumVIDEOIDX
mentionsarray[2 items]REL
locationgeo52.5,13.4IDX
engagementobject{…}
C.

Export pipeline

Once a story sequence is captured and structured, it leaves the viewer in whatever shape your downstream tools expect. Three primary formats, plus a raw dump for archival.

  • JSON — full fidelity, nested, ideal for programmatic analysis.
  • CSV — flat frame-level table, drops straight into Excel or Google Sheets.
  • ZIP media — every image and video frame, renamed by story ID and timestamp.
  • Raw snapshot — the original page responses, for evidentiary archival.
export.summaryREADY
FORMATSIZERECORDSBAR
JSON1.4 MB42
CSV0.4 MB42
ZIP320 MB128
RAW6 MB42
XLSX1.1 MB42

Four moves from handle to archive.

1

Enter the handle

Drop a username into the search field. Swioz resolves it against the source, confirms the profile is accessible, and shows you a preview card before any story capture begins.

Takes ~2 seconds
2

Pick your scope

Choose what you want to pull — active stories only, active plus highlights, full frame extraction including expired sequences. Date range optional.

5 toggles, 1 date range
3

Watch it unfold

The viewer streams frames in as they’re captured — you don’t wait for a finished file. Start searching, filtering and clicking into stories while the capture is still running.

Live, incremental
4

Export or stay

Download the structured story archive in the format you need, or keep the snapshot open in the viewer for as long as your session lasts. Captures can be re-opened from history.

JSON · CSV · ZIP · XLSX

Every part of the story, its own panel.

Hover any tile to focus. The mosaic is the viewer’s navigation — each panel is one of the nine data surfaces, opened individually but cross-linked by frame ID, sticker, location and timestamp.

Active stories panel
Panel 01
Active stories
Expired stories panel
Panel 02
Expired archive
Highlights panel
Panel 03
Highlights
Video stories panel
Panel 04
Video stories
Frame extraction panel
Panel 05
Extracted frames
Engagement panel
Panel 06
Engagement
Stickers panel
Panel 07
Stickers & Mentions
Link tracking panel
Panel 08
Link tracking
Export panel
Panel 09
Bulk export
Timeline panel
Overlay
Cross-source timeline

Eight reasons people open Swioz.

01
No login. Ever.
Swioz never asks for your credentials and never stores them. You don’t need an account on the source platform — paste a handle and the viewer takes it from there.
02
Preserves the ephemeral.
Stories vanish after 24 hours. Swioz captures them exactly as they appeared, preserving the sequence, duration, and metadata forever in a structured archive.
03
Respects rate boundaries.
The engine throttles itself. Captures don’t hammer the source, don’t trigger anti-bot walls, and don’t get your IP blocked. Slow is fast if slow actually finishes.
04
Read-only, by design.
Swioz cannot post, reply, follow, or interact. The viewer has no write path — which means there’s no path to misuse, ever, by anyone, including us.
05
Zero view footprint.
The account owner will not see that you viewed their story. Swioz does not register a view impression on the source platform, keeping your research completely passive.
06
Export anywhere.
JSON for engineers, CSV for analysts, XLSX for finance, ZIP for the archive shelf. One capture, four formats, no re-processing. Your downstream tools will thank you.
07
Highlight compilation.
Automatically detect which stories were added to highlights. Swioz links the ephemeral story to its permanent highlight counterpart, creating a unified timeline.
08
Built for repeat use.
Capture history is preserved per handle. Open a profile you viewed three months ago and the previous story snapshot loads instantly — no re-capture unless you ask for one.

Ephemeral data should be accessible, structured, and safe to explore. Swioz simply makes it readable.

Built for researchers, journalists, and analysts who need to view story data without writing brittle scripts or crossing ethical lines.

Things people ask before they paste a handle.

Swioz Viewer only reads data visible on the source profile. It does not bypass access controls, does not log in to any platform, and does not interact with protected content. You are responsible for complying with the terms of service of any source platform and with the data-protection laws that apply in your jurisdiction.
Yes. Swioz resolves handles directly — you don’t need to be signed in to the source platform, and you don’t need to give Swioz any credentials. If a profile’s stories are visible to a logged-out browser, they’re visible to the viewer.
No. Swioz does not generate view notifications, story impressions, or profile-visit signals on the source platform. The capture is passive — it reads what’s already there without registering as an interaction.
No. If an account is restricted, protected, or deleted at the moment of capture, Swioz returns an empty result. There is no fallback, no historical cache of hidden content, and no way to bypass privacy settings.
You can only download expired stories if they were captured by Swioz while they were still active. We do not have a magic archive of the internet’s deleted stories — we can only preserve what was accessible at the moment you ran the viewer.

Paste a handle. Watch the stories unfold.

No signup, no install, no credentials required. The story viewer opens in your browser and the first capture starts in seconds.