How to embed a form in Notion without broken blocks

Notion renders embeds through Iframely, a service that supports over 1,900 domains. Its help center gives the blunt explanation for failures: some websites prohibit their content from being embedded elsewhere. Technically, that site sends an X-Frame-Options or Content-Security-Policy frame-ancestors header telling browsers not to show it inside another page.

Before blaming the builder, rule out the simple causes. The form might still be a draft, set to private, restricted to people in your organization, or closed. The link might be an admin or edit link rather than the public one. Or you may have pasted the whole <iframe ...> snippet from the builder's embed panel; Notion wants the bare URL.

Open the form in Google Forms, click Send (or Publish, then copy the responder link), choose the link tab, and copy the viewform address. In Notion, type /embed and paste that link. Google's own embed tab gives you an <iframe> snippet; you can copy the src value out of it, which ends in ?embedded=true, but don't paste the whole snippet.

The embed works well for an open form: short answers, choices, scales, sections. It breaks when the form needs the respondent to sign in to a Google account. Google's help pages say a file upload question requires respondents to sign in, and so does the "Limit to 1 response" setting. Forms restricted to your Workspace organization need sign-in too.

Google's sign-in page refuses to load inside a frame. We checked its response headers on 28 September 2026: accounts.google.com returns X-Frame-Options: DENY and frame-ancestors 'none'. So the respondent sees the form's sign-in prompt inside Notion but can't finish signing in there. Notion adds its own caveat that embeds needing a login to an external site don't work in its desktop and mobile apps.

You have three options. Put a plain link or a Notion button above the embed that says "Open the form in a new tab", so people who hit the sign-in wall have a way through. Remove the settings that force sign-in, if you can live without them: swap the file upload question for a link to a shared folder, and drop the one-response limit. Or use a builder whose file uploads and duplicate checks don't depend on a Google account; our guide to Google Forms file upload without sign-in compares the options.

Usually, for public forms. The embed is a web page inside the page, so a form that works in a phone browser will generally display in the Notion app. Two things go wrong more often on mobile. Anything behind a login fails, per Notion's own note. And a fixed-height frame inside a scrolling Notion page creates two scroll areas, so respondents scroll the page when they meant to scroll the form.

If most respondents are on phones, a one-question-at-a-time form fits a short frame better than a long single page, or skip the embed and link to the form so it opens full-screen.

Notion launched Forms in October 2024 (release 2.46), and they are available on every Notion plan. A Notion form is connected to a database: each question is a database property and each response becomes a row, so there's nothing to embed and nothing to sync. For internal requests, RSVPs and feedback that you'll triage inside Notion anyway, that is hard to beat.

The limits are worth knowing before you commit. Conditional logic, where a question appears based on an earlier answer, is only on the Business and Enterprise plans. Responses from forms shared with anyone on the web are automatically anonymous. Removing Notion branding from a public form needs a paid plan. And you can't create or customize a form on a mobile device.

An external builder earns its place when you need logic on a Free or Plus workspace, a conversational layout, payments, quiz scoring, or respondents who shouldn't see a Notion page at all. Comparing Notion Forms against dedicated builders is a bigger topic than embedding, and we'll cover the Notion forms alternative question on its own page.

Yes, and it is often a better setup than an embed alone. The embed puts the form on a Notion page; an integration puts the answers into a Notion database where you can filter, assign and chart them. Notion Forms do this natively. Most external builders offer a Notion integration: Tally lists one on its free plan, and on Zunoform the Notion integration is part of Pro and Business, alongside the Google Sheets, Zapier and webhook options available on Free.

A common pattern is to embed the form on a public Notion page such as a team wiki or a client portal, and send responses to a private database that only your team can see.

Zunoform works as a Notion embed with no special setup: paste the form's /form/ link into an embed block. Its form pages don't send frame-blocking headers, respondents never need an account, and file upload works on every plan without a sign-in step (10 MB per file on Free). For duplicate control without Google accounts, one-response-per-person can match by email, by browser or with one-time links. You can use the conversational layout, which suits a short Notion block, or a single page.

Trade-offs: the embed doesn't resize itself, so size the block by hand. The Free plan is 500 responses a month; Tally has no monthly cap on free. And sending responses into a Notion database needs Pro ($14.99/mo). If your team lives in Notion and needs logic only occasionally, native Notion Forms may be enough.