Choosing a tool

Google Forms calculated fields: what works, and what doesn’t

Google Forms has no calculated field. There is no box that adds up a quantity times a price, or shows a quote while someone is filling in the form. There are still four ways to get a number out of responses, each computing it after the respondent has submitted. Here is how each works, and when you need a different tool.

By the Faldaro team · Published September 25, 2026

What Google Forms can and cannot calculate

Google Forms collects answers. It can validate them — a number within a range, text that matches a pattern — and in quiz mode it can score them. What it cannot do is hold a field whose value is computed from other answers. Every workaround below moves the arithmetic somewhere else, which has two consequences worth knowing before you choose:

• The respondent never sees the result while filling in the form. A quote, a total or a fee is computed after they press Submit.
• The computed number lives apart from the answers — in the quiz score, a sheet column or a script — so it is only as reliable as whatever computes it.

Option 1: quiz mode scoring

Turn the form into a quiz in Settings, give each question an answer key and a point value, and Google Forms adds up the points for each response. You can release the score immediately after submission, so the respondent sees it on the confirmation page.

This is the right tool for assessments, self-checks and simple eligibility screens. It is the wrong one for money: points only accrue for answers that match the key, so there is no way to multiply a quantity by a price, apply a percentage or cap a figure.

Option 2: a formula column in the linked sheet

Link the form to a Google Sheet and add a column that computes from the answer columns. Because each response is inserted as a new row, a formula in a single cell does not reliably follow new responses; write one ARRAYFORMULA in the header row so the whole column is computed at once:

=ARRAYFORMULA(IF(ROW(C:C)=1, "Total",
  IF(C:C="", "", C:C * D:D)))

This handles most internal needs: totals for a report, a fee to invoice, a score to sort by. Its limits are that the respondent sees nothing, anyone with edit access can change the formula or overwrite a result, and a renamed or reordered question can silently shift which column the formula reads.

Option 3: Apps Script on submit

An installable form submit trigger can compute a figure the moment a response arrives, write it to the sheet, and email it — to the respondent as a quote, or to your team:

// In the linked Google Sheet: Extensions → Apps Script.
// Add an installable "On form submit" trigger for this function.
function onFormSubmit(e) {
  const qty = Number(e.namedValues['Quantity'][0]);
  const price = 25;                       // the unit price lives here, in code
  const total = qty * price;

  e.range.getSheet()
    .getRange(e.range.getRow(), e.range.getLastColumn() + 1)
    .setValue(total);
}

A script can express any logic, and it keeps prices out of the form itself. The trade-offs are the ones every script carries: it runs as the person who created the trigger and stops if their account does, it works within Apps Script’s daily quotas, and when a question is renamed the key in e.namedValues changes and the script breaks until someone who understands it fixes it.

Option 4: a Marketplace add-on

Several Google Workspace Marketplace add-ons add calculations to Google Forms, typically by generating a companion form or a results page that can compute values. Before installing one, check what it can access (form, sheet and Gmail scopes are common), where the computation runs, whether respondents see the result before or after submitting, and how it is priced.

When you need a real calculated field

The workarounds above are fine for scoring and back-office totals. A calculated field is worth moving for when:

• People should see the number before they commit — a quote, a booking fee, a membership price.
• The number is charged, so it has to be the one the rules computed, not one anybody could change.
• The pricing is yours to keep — rates you would rather a competitor could not read from the page.
• Other rules depend on it: show a question over a threshold, route a large request for review.

How Faldaro handles calculated fields

In Faldaro a calculated field is part of the form, and its formula is evaluated on the server:

• Formulas reference fields by name — `quantity` * `unitPrice` — using arithmetic, comparisons and a closed set of functions (MAX, MIN, ROUND and a few more). Nothing in a formula can execute code, and every formula is checked when you publish.
• The public form can show the result as people type. With live evaluation switched on for a link, the server returns the computed values on each change — the values only, never the formula behind them.
• The submitted figure is the server’s. Every save re-runs the formulas and stores the result separately from the answers, so a total edited in the browser is replaced by the real one. A payment is priced by the same engine.
• Hidden questions count as zero, so a total stays correct when conditional logic hides an add-on the respondent did not choose.

The quote calculator page shows a working example, and calculated fields are on every plan, the Free plan included.

For a calculator that needs no account and no server at all — a bill splitter, a quick estimate to send around a group — Faldaro Zero runs the same formulas inside a link. One honest trade: in Zero the formula travels with the form, so anyone holding the link can read it. Pricing you would rather keep private belongs on Faldaro, where the server holds the formula and returns only the values.