Embed a public link on your website
Drop a public signing link into your own page with one iframe snippet, after adding your site to the allowed origins list.
Every public link comes with a second URL and a ready-made iframe snippet, so the same signing flow can live on your own page instead of ours. One thing has to happen first: your site has to be on the workspace's list of allowed origins, or the browser refuses to render the frame.
Who can embed a public link
Available on Business and above, the same plan that includes public links. You need a link already published, as covered in create a public signing link. Editing the allowlist is a workspace admin job, since it applies to every embedded signing page the workspace serves.
Allow your site to frame the page
-
Go to Settings > Developers > Embedding.
-
Type the full origin of the page that will hold the frame, for example https://www.yourcompany.com. Only https is accepted.
-
Click Add, repeat for any other host you serve from, then click Save origins.
An empty list means embedded signing is off for the whole workspace, and the page says so in plain words. Removing an origin later takes effect as soon as you save.
Copy the snippet
Open Public links, click your link, and look at Embed on your site on the Overview tab.
Two things sit there. First the embed URL, which is the same link on a path browsers are allowed to frame. Below it is the whole iframe tag, already pointing at that URL, sized to 100 percent wide and 700 pixels tall with no border. Click Copy next to the snippet and paste it into your page where the form belongs.
If your workspace has no origins saved yet, a red notice appears right under the snippet with a link into the Embedding settings. Sort that out before you paste anything, otherwise the frame renders empty with only a console error to explain itself.
What your visitors get
The framed page shows your workspace branding, the document name, a Full name box and an Email address box. After Continue to signing, the frame itself moves on to the signing view, so the visitor never leaves your page. Nobody has to register for anything, which is the same story everywhere in the product: see do signers need an account. Each visit creates its own document, and you track them all on the link's Documents tab.
Usage is shared between the two URLs. A Max uses cap of 50 covers 50 documents in total, however they were started, and an expiry date closes both at the same moment. The caps themselves, and what each plan includes, are in template limits by plan.
If something goes wrong
- The frame is blank and the console mentions frame-ancestors. Your page's origin is not on the list, or it was saved under a different host such as the bare domain instead of www.
- It works locally but not in production. Localhost is not on the list by default, and neither is your staging domain. Add each one you test from.
- You added the origin but nothing changed. The Add button only stages an entry. Click Save origins, and the label reading "Unsaved changes" disappears when it lands.
- A visitor sees "This link isn't available". The link behind the embed has been disabled, expired or used up. Check its status badge on the link page.
- The form is cut off at the bottom. Raise the height in the snippet you pasted. 700 pixels suits a short document, not a ten-page one.
Frequently asked questions
Why must I list my site before the embed works?
A signing page inside somebody else's frame is a clickjacking target, so framing is off until a workspace admin names the sites allowed to do it. With an empty list, browsers refuse to render the frame at all and the visitor sees a blank box.
Can I embed on http or on a page without a domain?
No. Only https origins are accepted, and each entry has to be a full origin such as https://www.yourcompany.com, with no path after it. Add every host you actually serve from, since www and the bare domain count as two different origins to a browser, and so does a staging subdomain.
Does the visitor sign inside the frame or somewhere else?
Inside the frame. After they enter their name and email, the frame moves straight to the signing view on your page, so nothing opens in a new tab. Their signed copy still arrives by email once the document is complete.
How tall should the iframe be?
The copied snippet uses 700 pixels, which fits the landing form and most one-page documents. Give it more height, or let it fill a container, if your document runs long. Width is already set to 100 percent so it adapts to your layout.
Do I need a separate link for the embed?
No. One public link serves both. The plain URL is for sharing in an email or a chat, and the embed URL is the same link on a path browsers are allowed to frame, so usage counts, expiry and Max uses apply to both together.
Keep going
Create a public signing linkBusiness and up
Publish a template as a link anyone can open. The visitor fills one role and signs on the spot, and the co-signers you named are emailed in turn.
ReadTemplate limits by plan
How many templates each plan saves, how many rows fit in one bulk send, and which plans include public links. With the rules that decide what counts.
ReadSend a document from a template
Click Use template, type the real name and email behind each role, and send. Fields, subject, signing order and expiry all come from the template.
ReadDo signers need an account?
No. Signers open the link in the request email and sign in the browser. Here is what gets recorded, what makes it legally valid, and when an account is worth having.
Read