# Share a public link

Open the same form to anyone — copy the link, embed it, or print a QR code.

## Share a public link

The second channel: a share link anyone can open, any number of people, any number of times. Same form, same answers inbox — no named recipient and no callback.

<h2 id="copy">Copy the link</h2>

Share</strong> and pick the <strong>Public link</strong> channel to find it.",
    },
    {
      title: 'Copy it',
      description:
        'That URL is live. Open it in a new tab and answer it once — that is the first row you will see on the next page. Then send it, post it, or put it behind a button.',
    },
    {
      title: 'Name it if you plan to make more',
      description:
        'One form can have several share links, each with its own settings and analytics. <strong>Create new link</strong> adds one; <strong>Link name</strong> labels it — "Newsletter", "Social Media". The name is yours only; respondents never see it.',
    },
  ]}
/>

<h2 id="ways">Three ways to put it in front of people</h2>

<h2 id="limits">Per-link settings</h2>

<p>Each share link carries its own settings, grouped into Link, Query parameters, Appearance, and Limits:</p>

<ul>
  <li>
    <strong>Set expiration date</strong> — the link stops working after this date.
  </li>
  <li>
    <strong>Limit response slots</strong> — how many response slots this link hands out. A started response claims a slot even if it is
    never submitted. <a href="/sharing-publishing/response-limits">Response limits →</a>
  </li>
  <li>
    <strong>Default language</strong> — which translation the link opens in; respondents can still switch from the picker.
  </li>
  <li>
    <strong>Query parameters</strong> — UTM values and hidden-field values appended to the URL, so you can tell campaigns apart.{' '}
    <a href="/building-forms/hidden-fields">Hidden fields →</a>
  </li>
</ul>

<p>
  A link with responses is <strong>revoked</strong> rather than deleted: it stops accepting new ones but keeps its analytics, and you can
  re-activate it later.
</p>

<p>
  <a href="/sharing-publishing/sharing-embedding">Share links →</a>
</p>

> ℹ️ **Which channel should this be?**
> <p>
>     Use a <strong>share link</strong> when anyone may answer and you do not know who in advance. Use a{' '}
>     <a href="/getting-started/send-your-first-request">request</a> when one named person owes you one answer and your workflow needs to know
>     when it arrives. Both spend from the same monthly allowance, and both land in the same inbox.
>   </p>

<h2 id="next-steps">Next steps</h2>
<div class="not-prose grid gap-3 sm:grid-cols-2">
  - [See answers arrive](/getting-started/see-answers-arrive) — Where responses from both channels land
  - [Embedding & popups](/sharing-publishing/embedding-popups) — Put the form on your own site
  - [Response limits](/sharing-publishing/response-limits) — Cap how many responses a link accepts
  - [Custom domains](/branding-domains/custom-domains) — Serve the form from your own domain (Pro)
</div>