Skip to content
SaveHQ logo

SaveHQ

Saves reels, links and photos sent by direct message into sorted collections and shared boards.
At a glanceswept Oct 26, 2026

not read yet

Use

For
People and friend groups saving reels, links and places they share over chat apps
Runs as
API
Used for
  • Save reels, photos and links by sending them in chat
  • Build shared lists for trips, dinners and watchlists
  • Sort saved restaurants, shows and recipes into collections
Worth knowingcomputed from what we read · each with its source
How a program reaches itfound, not claimed · read Oct 27, 2026
  • MCP serverapp.savehq/savehqverified in the MCP registry
  • Stateanswers, requires sign-inchecked 2026-10-27
  • Address to connectsavehq.app/api/mcp
  • OpenAPI spec57 pathsthe spec ↗

MCP server details →

This card as JSON, for your agent →

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.

Alternatives in Creative & mediaby use, among tools still maintained

Figure and bar: visits/mo, estimate · year: online since

Compare SaveHQ with

Pick up to two.

All 10 alternatives to SaveHQ →

All Creative & media tools →

Not it? Say what you need

beta

Three tools from the Atlas for the job you describe, each with what fits and what does not.

From people who use itnot part of the reading

No notes yet. What do you use SaveHQ for?

Sign in to leave a note
Questions this page answers
  • What is SaveHQ?

    Saves reels, links and photos sent by direct message into sorted collections and shared boards. It is listed in the Atlas under Creative & media.

  • Who is SaveHQ for?

    People and friend groups saving reels, links and places they share over chat apps

  • Do people use SaveHQ?

    Little sign of use.

  • What are alternatives to SaveHQ?

    In Creative & media, by use: Linko, Vídeos temporales, Diagram, MaxVideoAI, gethumandesign, Prelo.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.

How we read every tool → · By INITE Atlas Desk