Swioz Viewer — See every signal from any connected account
SWIOZ / VIEWER v3.2
INDEX — 01 / 09
Account data, fully unfolded

See every signal from any connected account.

Swioz Viewer is a read-only exploration surface for publicly available account data. Drop in a handle, pull the thread, and watch an entire profile unfold into a structured, searchable, exportable archive — no logins, no API gymnastics, no leaving a footprint.

Open the viewer → See how it works
View postsView storiesView highlightsView reelsView taggedView commentsView captionsView timestampsView engagementView metadata View postsView storiesView highlightsView reelsView taggedView commentsView captionsView timestampsView engagementView metadata
02 — What it does

Nine surfaces. One viewer.

Every public-facing layer of a connected account, broken out into its own inspectable panel — searchable, filterable, and exportable on demand.

01 / 09

Post archive

Browse every published post in a chronological grid or list view. Captions, alt text, location tags, and timestamps are preserved exactly as they appeared at the moment of capture.

Grid · List · Timeline
02 / 09

Story reels

View active and expired story sequences as they were originally published. Each frame is timestamped, ordered, and presented with its original duration intact.

Active · Expired · Saved
03 / 09

Highlight collections

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

Covers · Titles · Order
04 / 09

Video reels

Play back short-form video content inline with full metadata. View counts, audio references, and cross-posting markers are surfaced alongside the player.

Inline · Metadata · Audio
05 / 09

Comment threads

Expand any post to reveal its full comment tree — top-level replies, nested responses, timestamps, and engagement counts on each individual reply.

Threads · Replies · Counts
06 / 09

Engagement metrics

See reaction totals, interaction ratios, and per-post engagement breakdowns. Compare side-by-side across any date range or content category.

Reactions · Ratios · Compare
07 / 09

Location index

Every geotagged post is plotted on a single map. Click a pin to jump straight to the original post, or filter the entire archive by location.

Map · Pins · Filter
08 / 09

Tagged mentions

Surface every post where the account has been tagged by others. A complete cross-section of how the profile appears across the wider network.

External · Network · Mentions
09 / 09

Bulk export

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

JSON · CSV · ZIP
03 — In depth

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 pages into queryable records, and an export pipeline that hands you back clean data.

A.

Capture engine

Swioz reads only what is already public. 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 posting, no interaction with the source account.
  • Rate-aware. Requests are throttled and spaced to stay within the source’s own publishing rhythm.
  • Idempotent. Re-running a capture on the same handle produces a deterministic diff against the previous snapshot.
  • Timestamped. Every record carries the exact moment it was observed, not the moment it was published.
capture.log LIVE
IDSOURCESTATUSRATE
#0142 profile/handle 200 OK 1.2s
#0143 posts/page-1 200 OK 0.9s
#0144 posts/page-2 200 OK 1.4s
#0145 stories/active 200 OK 0.6s
#0146 highlights/all 200 OK 1.1s
#0147 reels/index 200 OK 1.3s
#0148 tagged/external 200 OK 2.0s
B.

Structuring layer

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

  • Unified schema. Posts, stories, reels and comments 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 is content-addressed, so duplicates across posts are detected automatically.
  • Caption parsing. Hashtags, mentions and URLs are extracted into their own queryable fields.
schema.json TYPED
FIELDTYPEEXAMPLEINDEX
id uuid a3f… PK
posted_at datetime 2025-03-14 IDX
caption text “nice light” FTS
hashtags array [3 items] IDX
media array [2 items] REL
location geo 52.5,13.4 IDX
engagement object {…} —
C.

Export pipeline

Once an account 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 post-level table, drops straight into Excel or Google Sheets.
  • ZIP media — every image and video, renamed by post ID and timestamp.
  • Raw snapshot — the original page responses, for evidentiary archival.
export.summary READY
FORMATSIZERECORDSBAR
JSON 4.2 MB 1,284
CSV 1.1 MB 1,284
ZIP 820 MB 3,902
RAW 14 MB 1,284
XLSX 2.4 MB 1,284
04 — How to use it

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 account is public, and shows you a preview card before any capture begins.

Takes ~2 seconds
2

Pick your scope

Choose what you want to pull — posts only, posts plus stories, full archive including tagged content. Date range optional. The viewer estimates capture time up front.

5 toggles, 1 date range
3

Watch it unfold

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

Live, incremental
4

Export or stay

Download the structured 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
05 — A session in snapshots

What a capture looks like, laid out on the desk.

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

POST
Captured post
morning light, 03·14
STORY
Captured story
2am, can’t sleep
REEL
Captured reel
walk home, 0:42
HIGHLIGHT
Captured highlight
lisbon, day three
TAGGED
Tagged post
found by @n.k.
POST
Captured post
new leaf, finally
STORY
Captured story
show, 11:30pm
POST
Captured post
brutalist block
REEL
Captured reel
kitchen, 0:18
HIGHLIGHT
Captured highlight
august, recap
POST
Captured post
self, in window
TAGGED
Tagged post
group show, may
9
Data surfaces
per capture
4
Export formats
JSON · CSV · ZIP · XLSX
0
Write operations
read-only, always
100%
Public-source only
nothing behind a login
06 — Surface by surface

Every part of the profile, 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 post ID, hashtag, location and timestamp.

Posts panel
Panel 01
Post archive
Stories panel
Panel 02
Stories
Highlights panel
Panel 03
Highlights
Reels panel
Panel 04
Reels
Comments panel
Panel 05
Comment threads
Engagement panel
Panel 06
Engagement
Location panel
Panel 07
Location index
Tagged panel
Panel 08
Tagged mentions
Export panel
Panel 09
Bulk export
Timeline panel
Overlay
Cross-source timeline
07 — Why use it

Eight reasons people open Swioz instead of a tab and a spreadsheet.

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 public handle and the viewer takes it from there.
→
02
Structured from the start.
You’re not parsing HTML or reverse-engineering endpoints. Every record arrives typed, indexed and cross-linked — ready to filter, sort, or export without a single line of glue code.
→
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, like, follow, comment or message. The viewer has no write path — which means there’s no path to misuse, ever, by anyone, including us.
→
05
Diff-aware snapshots.
Run the same handle twice and Swioz shows you exactly what changed — new posts, deleted posts, edited captions, engagement deltas. A living archive, not a frozen one.
→
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
Cross-source timeline.
When the same account appears on multiple supported sources, Swioz merges their posts into a single unified timeline. One profile, one chronology, one export.
→
08
Built for repeat use.
Capture history is preserved per handle. Open a profile you viewed three months ago and the previous snapshot loads instantly — no re-capture unless you ask for one.
→
08 — Questions

Things people ask before they paste a handle.

Swioz Viewer only reads data that the source account has already chosen to make public. It does not bypass access controls, does not log in to any platform, and does not interact with private or 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 — GDPR, CCPA, and equivalent. If you’re unsure, ask a lawyer before using captured data commercially.
No. Swioz resolves public 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 is visible to a logged-out browser, it’s 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.
Swioz supports any public profile from a list of compliant sources that is updated regularly. The current list is published in the viewer’s source-picker. If a source isn’t listed, it’s because we haven’t yet verified that our capture pipeline respects its rate boundaries — we add sources only when we’re confident the engine is safe to run.
Snapshots stay in your session history for 30 days. If you download the export, the file is yours to keep indefinitely. We don’t retain captures on our side beyond the session window — once your session ends and the 30-day window closes, the structured data is gone from our infrastructure.
Yes, subject to the terms of the source platform and your local data-protection law. Swioz is built for journalists, researchers, analysts and archivists who need structured public-data access. It is not built for surveillance, harassment, or redistribution of personal data — the usage policy is enforced.
No. If an account is private, protected, or deleted at the moment of capture, Swioz returns an empty result. There is no fallback, no historical cache of private content, no way to recover deleted posts that were never captured while public.
09 — Begin

Paste a handle. Watch the account unfold.

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

Open Swioz Viewer → Read the feature list
Read-only · Public-source · No credentials · Session-based