DEV Community

XZMHXDXH
XZMHXDXH

Posted on

Building a cleaner public Instagram reference workflow

Creators, marketers, and research teams often need to collect public social media references: a reel used in a campaign, a profile picture for a contact sheet, or a public post that needs to be reviewed later.

The annoying part is not usually the media itself. It is the workflow around it: browser extensions, account logins, mobile-only flows, watermark-heavy tools, and pages that make it unclear what is public content and what is not.

I built IGPorter as a small browser toolkit for that specific public-content workflow. Paste a public Instagram URL or username, preview the available public media, and save assets when Instagram returns them. It covers public stories, highlights, reels, videos, photos, carousel posts, and profile pictures.

A few product decisions were intentional:

  • No Instagram password or account session is required.
  • Private accounts stay private.
  • The tool is browser-based, so there is no extension or mobile app to install.
  • The copy and UX stay explicit about public URLs and reuse responsibility.

The biggest lesson from building it was that boundary-setting is part of the product. For tools around social platforms, a cleaner UX is not just fewer clicks. It is also making the allowed workflow obvious, keeping user expectations grounded, and avoiding claims that imply access to restricted content.

If you work with public social media references, I would love feedback on which edge cases matter most: stories, highlights, carousels, profile media, or bulk organization after saving.

Top comments (0)