Swioz Profile Viewer Online New & Updated
SWIOZ / PROFILE VIEWER V3.2
READ-ONLY INSTRUMENT
Profile data, fully unfolded

SWIOZ PROFILE VIEWER.

A read-only exploration surface for profile data. Drop in a handle from any supported network to instantly view posts, stories, media, and metrics in one structured, searchable archive. No logins. No footprints. No credentials required.

VIEW PROFILESVIEW POSTSVIEW STORIESVIEW HIGHLIGHTSVIEW MEDIAVIEW METRICSEXPORT JSON VIEW PROFILESVIEW POSTSVIEW STORIESVIEW HIGHLIGHTSVIEW MEDIAVIEW METRICSEXPORT JSON

What a profile capture looks like.

Each card below is one piece of a profile 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
Profile post capture
morning light, 03·14
STORY
Profile story capture
2am, can’t sleep
REEL
Profile reel capture
walk home, 0:42
HIGHLIGHT
Profile highlight capture
lisbon, day three
TAGGED
Profile tagged capture
found by @n.k.
POST
Profile post capture
new leaf, finally
STORY
Profile story capture
show, 11:30pm
POST
Profile post capture
brutalist block
REEL
Profile reel capture
kitchen, 0:18
HIGHLIGHT
Profile highlight capture
august, recap
POST
Profile post capture
self, in window
TAGGED
Profile tagged capture
group show, may

Nine surfaces. One viewer.

Every layer of a connected profile, 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 profile 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 profile snapshot as JSON, CSV, or zipped media. 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 pages 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 posting, no interaction with the source profile.
  • 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.logLIVE
IDSOURCESTATUSRATE
#0142profile/handle200 OK1.2s
#0143posts/page-1200 OK0.9s
#0144posts/page-2200 OK1.4s
#0145stories/active200 OK0.6s
#0146highlights/all200 OK1.1s
#0147reels/index200 OK1.3s
#0148tagged/external200 OK2.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.jsonTYPED
FIELDTYPEEXAMPLEINDEX
iduuida3f…PK
posted_atdatetime2025-03-14IDX
captiontext“nice light”FTS
hashtagsarray[3 items]IDX
mediaarray[2 items]REL
locationgeo52.5,13.4IDX
engagementobject{…}
C.

Export pipeline

Once a profile 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.summaryREADY
FORMATSIZERECORDSBAR
JSON4.2 MB1,284
CSV1.1 MB1,284
ZIP820 MB3,902
RAW14 MB1,284
XLSX2.4 MB1,284

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 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

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

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
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.

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

Built for researchers, journalists, and analysts who need to view profile 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.
No. 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 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 accessible 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.
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, no way to recover deleted posts that were never captured while accessible.

Paste a handle. Watch the profile unfold.

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