Skip to main content
Shareable hosts static HTML, but your page can still be interactive. Anything a third party offers as an embed — an <iframe> snippet or a script + form — works on a Shareable page, because the other service runs the logic and stores the data. Shareable just serves your HTML, embed and all.
New to this? Start with the Cookbook — step-by-step recipes for a contact form, booking page, newsletter, payments, and more. This page is the reference list of what’s possible.

​
You don’t add it — your AI does

A page is just HTML, so the simplest path is to ask the AI that builds your page to include the integration:
“Build an RSVP page with a Google Form.” · “Add a Calendly booking widget.” · “Embed this YouTube video and a newsletter signup.”
Claude, ChatGPT, or Gemini writes the embed into the HTML, you publish, and it works — nothing to configure in Shareable.

​
Forms — the most common case

​
Google Forms, Typeform, Tally, Jotform
Paste the provider’s <iframe>. It renders in a sandboxed frame and submits directly to the provider.
​
Formspree, Tally, Basin
A plain <form> that posts to a form-handling service.

​
What else you can embed

The same approach covers most “interactive” things on a page:
Rule of thumb: if a service gives you an “embed” / <iframe> snippet or a paste-this-script widget, it’ll work on a Shareable page.

​
What Shareable does not do

We don’t store submissions, process payments, or send emails on your behalf — the embedded service owns all of that. Shareable stays a simple, fast, static host; the provider handles the data. That separation is what keeps your page portable and dependency-free.
Iframe embeds are cross-origin and sandboxed — the safe default. A pasted external <script> runs in the page itself, so only embed scripts from services you trust. Keep the rest of the page self-contained (inline your CSS/images); the embed is the one thing that loads from another domain.