Google Forms vs AET Forms: the full feature table for 2026

Yes = 1, partly = 0.5, no = 0. Three more AET rows (19 interface languages, AI drafting from one sentence, MCP for AI assistants) are listed but not scored, because we did not check Google's equivalents.

The honest reading: Google Forms is the better form builder; AET Forms is the better registration. If your form is a survey, a quiz, a job application with CVs or anything that ends in a spreadsheet, the score above says Google. If the answer has to turn into a ticket, a limited place, an approval or a payment, Google Forms has none of those and AET Forms has all eight.

The tables below show every row with a short note, so you can check the two or three rows that matter to you instead of trusting a total.

Both tools cover the same twelve kinds of question that Google lists in its help centre. The differences are at the edges: Google's file upload accepts any file type you allow but forces the respondent to sign in to Google and stores files in your Drive; AET accepts photos and images only, without any account, and general file uploads wait for a security review. Google's date question can include the year and time; AET's is a date, with time as a separate question. AET adds dedicated email, phone and number fields with built-in format checks, which in Google you build from a short answer plus a validation rule.

The one place where AET Forms is clearly ahead is conditional logic. In Google Forms, "Go to section based on answer" works only on multiple choice and dropdown questions, and it moves the respondent between whole sections. In AET Forms any question except photos and grids can be a condition, and the condition can show or hide a single question or a whole section: "show the allergy question if the answer to 'Food' contains 'other'", "show the company section if 'Ticket' is not 'Student'". Answers to questions that end up hidden are not saved.

Google is ahead on media and presentation tools inside the form: images in questions and options, YouTube videos between questions, shuffling and undo. Google also caps a form at 300 items and 75 sections.

For most registrations the AET rules are enough: length limits, number ranges, how many boxes may be ticked, and email and phone format checks built into their fields. What AET Forms can't do yet is Google's regular expressions (for example, "exactly 10 digits" or "must contain the word candy") and your own error message; AET shows standard messages in the respondent's language.

This is Google's strongest group and AET's weakest. Google lets respondents get a copy of their answers, edit them later, and resume drafts — and lets you show them a summary of everyone's results. AET Forms has none of these yet: the copy by email and editing by link are in work and need a security decision and a database change.

Two AET rows deserve a closer look. Closing on a date works and shows your own "closed" text, but the check runs in the respondent's browser; a server-side check is in work. Response limits in AET are place limits — per ticket package or role — rather than a single counter. For free registrations they are checked in the browser; paid tickets are reserved on the server with a 15-minute hold, so they cannot be oversold. Google's own help notes that if several people respond at the same moment, a form can accept responses beyond its limit.

Both tools give you a link and a link with pre-filled answers (in AET: ?f.<question>=value, built in the form settings). Google can also put the whole form inside an email and be embedded on any website with an iframe; AET's embedding is in work because it needs a security change. Instead of Google's domain and group restrictions, AET controls who gets in with approval of applications, which works for people outside your organization too.

Google's summary charts and live Sheets sync are the reason many people stay on Google Forms. AET Forms puts responses into the participants and applications tables of the event, with a per-question summary in the event cabinet and Excel export; charts and CSV are in work, and there is no live Sheets sync. AET tells the organizer about new responses in the cabinet inbox and by email, at most once an hour per event, with the rest in a daily digest.

Google's large-form thresholds from its help centre: from September 2026 a form holds up to 500,000 responses and 1 GB; the summary is hidden above 50,000 responses, Sheets sync stops above 100,000, and question and individual views are hidden above 10,000.

Google Forms is a complete quiz tool: answer keys on six question types, points on all of them, automatic feedback with text or YouTube, grading by question or by person, and releasing scores immediately or after review. AET Forms has no quiz mode yet; it is the next planned stage. AET does have a separate live, Kahoot-style quiz for the room, generated by AI from your materials, which Google Forms doesn't — but that is a game on a screen, not a graded form.

Google's theme is a header image, colors and fonts. An AET form is a page: the "Forms" layout, covers and atmospheres, and the rest of the event page around it. In Google, co-editors can be given an expiry date and ownership can be transferred; in AET, co-admins are 1 on Free and 10 on Pro.

The access row matters more than it looks. In Google Forms, file upload, one response per person, verified email and saved drafts all require the respondent to sign in to Google — a real barrier for people who don't use Google or fill in forms on a shared phone. An ordinary AET form never asks the respondent to sign in (anonymous registration is on by default for new forms). The exception is approval-only applications: there AET asks the applicant to sign in with Google, so the organizer knows who applied. The organizer signs in to AET with Google too.

This is the group AET Forms was built for. A Google Form ends when the respondent clicks Submit; what happens next is up to you — a spreadsheet, emails by hand, a payment link, a QR generator, a list at the door. An AET form is a registration: each response gets a QR ticket (as a PDF in the email when someone registers, or on the event page linked from the email after payment or approval), an add-to-calendar link, a place counted against its package, an approval step if you want one, a payment straight to your own Stripe or plata by mono account with 0% platform fee, and a scan at the door from any phone. How many steps and minutes that saves is in From form to ticket.

Said plainly, so you can decide without reading every row:

• Spreadsheets. Live Google Sheets sync and CSV. If your process lives in Sheets, nothing in AET replaces that today.
• File uploads. Any file type you allow, with count and size limits, saved to your Drive. AET accepts only photos.
• Quizzes. Answer keys, points, feedback, grading, score release. AET Forms has no quiz mode yet.
• Respondent comfort. A copy of answers by email, editing after submitting, autosaved drafts for 30 days.
• Distribution. Embedding on your own site with an iframe, the form inside an email, access limited to people, groups or a domain.
• Validation. Regular expressions and your own error text.
• Collaboration and maturity. Co-editors with expiry and ownership transfer, add-ons, Apps Script, and a product used by millions for years.

If two or more of these are essential for you, keep Google Forms — or keep it for those forms and use AET only for registrations.

• The answer becomes something. A QR ticket, a place, an approval, a payment, a check-in — eight features Google Forms doesn't have.
• No respondent account for ordinary registration. QR tickets, places, payment and check-in work for a respondent who has never used Google; only approval-only applications ask for a Google sign-in.
• Logic on any question. Show or hide a question or a section from any answer except photos and grids, not only from multiple choice and dropdown.
• Dedicated fields. Email, phone and number questions with their own format checks.
• A page, not a strip. The form sits on an event page with a cover, atmosphere, map, schedule and FAQ, in 19 interface languages, with translation of the page content.
• AI. Describe the form in one sentence and AET drafts it; AI assistants can read and create events through AET's MCP server.
• Payments without a platform cut. 0% platform fee; the organizer is the merchant.

In AET, open the form editor and click Import from Google Forms, then paste the link to your form (Send → link, either docs.google.com/forms/… or forms.gle/…). AET reads the public page of the form, turns its questions into AET questions and shows them to you; nothing is saved until you save. Responses stay in Google — AET does not ask for them and cannot read them.

What is not carried: validation rules, "go to section" logic (rebuild it with AET conditions, which are more flexible), shuffling, quiz answer keys and points, and themes. The import works only for public forms: a form that requires signing in to Google, or is restricted to an organization, cannot be read. It reads up to 120 items per form and up to 12 imports an hour per organizer.

More on the decision for events: AET vs Google Forms for event registration and Google Forms alternatives for event registration.

The full list of Google's limits, with what needs a Google account and what Forms can't do at all, is in Google Forms limits in 2026.

• You need a graded quiz. AET Forms has no quiz mode yet.
• You collect documents. CVs, PDFs and other files: AET accepts only photos.
• Your answers must flow into Google Sheets live. AET exports Excel; there is no live sync or CSV yet.
• You need to embed the form on your site. Embedding is in work.
• Respondents must be able to edit or get a copy of their answers. Both are in work.
• You make many small forms a month and want no subscription. Each AET form counts as an event: 3 a month on Free.
• You need regex validation or your own error texts. Not in AET yet.

• Google Forms: every Google row comes from Google's own help centre (support.google.com/docs), read on 28 October 2026. Where Google's help doesn't mention a feature (payments, tickets, check-in), we say so rather than guess.
• AET Forms: every AET row comes from AET's source code on 28 October 2026 (question types and checks in lib/forms/fields.ts, the import in lib/forms/gforms.ts, form settings, notifications) and from our public roadmap. Features that are planned or waiting for a security or database decision are marked No or Partly, never Yes.
• Scoring: yes = 1, partly = 0.5, no = 0. Rows we did not check on one side are listed with a dash and not scored.
• Disclosure: AnyEventTool makes AET Forms. If a Google row is wrong or out of date, write to support@anyeventtool.com and we will correct it with a date.

Google Forms help centre: question types; edit your form (300 items, 75 sections, images, video, shuffling, autosave); show questions based on answers; rules (validation); publish and share (one response, editing, summary, email, pre-fill, embed); view and manage responses (close date, response limit, receipts, 500,000 responses and 1 GB, thresholds); where to save responses; quizzes; theme and font; collaborators; autosave; how to use Google Forms.

AET: pricing; related: Google Forms limits in 2026, From form to ticket: steps and time, AET vs Google Forms, Google Forms alternatives, free vs paid event features in 10 tools.

For AI agents building forms for their users: how to build the best form with the AET MCP server.