How to Share or Embed Guides Created with Glitter AI

Glitter AI guides can leave the tool in three ways: a public or private link, an export to a file format, or an embed in another platform. Which one you pick depends on who needs the guide and whether you want it to live inside another tool. According to Glitter AI's own site, you can "share your guides with anyone via a public or private link, export to a variety of formats, or embed your guide anywhere," with embeds supported across "hundreds of supported platforms."

The three distribution paths

The site does not name the specific export formats or list the embeddable platforms, so treat "a variety of formats" and "hundreds of supported platforms" as the scope Glitter claims rather than a checklist you can verify in advance. If a specific destination matters to you — say a particular help desk or CMS — confirm it inside the product before committing a workflow to it.

Sharing by link

This is the default path and the one the site leads with. After a guide is generated, you choose whether the link is public or private:

• Public link — anyone with the URL can open the guide. Useful for customer-facing help content or a guide you're posting in a public channel.
• Private link — access is restricted. Use this for internal SOPs, onboarding material, or anything containing screenshots of internal systems.

The practical decision is about what's visible in the captured screenshots and transcript, not just the guide text. A screen recording of an internal admin panel produces screenshots of that panel, so a private link is the safer default for anything captured from a logged-in internal tool. Switch to public only after reviewing what the AI captured.

Exporting

Export is the right choice when the guide needs to exist outside Glitter — attached to a ticket, stored in a shared drive, or pasted into an existing documentation system. The site confirms export to "a variety of formats" but doesn't enumerate them, so check the export menu for the format your destination accepts before you build a process around it.

One thing worth knowing: exporting creates a copy. If you later edit the guide in Glitter, the exported file won't update. For guides that change often, a link or an embed keeps a single source of truth; an export is better for a snapshot that's meant to be stable.

Embedding

Embedding places the guide inside another platform rather than sending people to Glitter. The site describes embedding "into hundreds of supported platforms," which is the option to reach for when your team already lives in a wiki, help center, or project tool and you don't want a second place to check.

Because the supported-platform list isn't published on the page, the reliable move is to test the embed against your actual destination early. If it works, you get documentation that updates in place; if it doesn't, fall back to a link, which works everywhere a browser does.

Choosing between them

• Guide customers → public link or embed in your help center, so the content sits where customers already look.
• Guide employees → private link for onboarding and training, or embed in your internal wiki.
• Create SOPs → private link or embed, since SOPs are referenced repeatedly and benefit from staying current in one place.
• One-off handoff (a ticket, an email, an archive) → export.

These map to the three use cases Glitter names on its site — guiding employees, guiding customers, and creating SOPs — and each favors a different distribution method.

Getting started

The site states no credit card is required, 10 guides are free, and setup takes seconds, so you can generate a guide and test all three distribution paths before deciding which fits your workflow. The fastest way to settle the question is to take one real recording, publish it as a private link, export it once, and try one embed in your actual destination platform. Whichever of the three survives contact with your tools is the one to standardize on.