GCD in Google Sheets: Common Factors and Reduced Ratios

• Introduced: first service launch date is not established by the official history reviewed; no numbered desktop introduction is assigned.
• Availability: documented in the rolling Google Sheets service. Examples use ordinary web-spreadsheet numeric cells; other clients and imported files are not separately certified.
• Checked: October 14, 2026; official GCD reference. Documentation and independent calculations, without native Sheets execution.

=GCD(value1, [value2, ...])

The first argument is required; additional numbers or ranges are optional. Google explicitly documents silently truncating decimal parts. =GCD(48.9,72.7) therefore uses 48 and 72, with expected result 24. It does not preserve fractional units or round the values to their nearest integers.

The practical examples below use positive integer counts. Google’s dedicated page does not state a complete native negative-input, text, error or magnitude-limit table. Do not transfer a numeric limit from another spreadsheet product and label it as a verified Sheets restriction.

Enter the following values:

Put the numeric counts themselves in B2:B3. Then calculate:

=GCD(B2:B3)
=B2/GCD(B2:B3)
=B3/GCD(B2:B3)

Expected results: 24 groups, 2 red per group and 3 blue per group. The total pieces per group are five, not 24. Every piece is used and every group has the same composition.

Twelve identical groups are also possible, with four red and six blue in each. GCD supplies the greatest possible group count, rather than every feasible grouping.

Add 60 green pieces in B4. =GCD(B2:B4) now has expected result 12, with per-group counts 4, 6 and 5. The former 24-group plan would need 2.5 green pieces in each group, violating the whole-piece requirement.

If the third count is 35 instead, =GCD(48,72,35) has expected result 1. The three counts share no divisor larger than one. GCD does not ignore a troublesome count to retain the earlier grouping.

A mixture uses 90 units of one ingredient and 150 of another. Their common divisor is:

=GCD(90,150)
=90/GCD(90,150)
=150/GCD(90,150)

Expected results are 30, 3 and 5, so the reduced ratio is 3:5. Keep the two reduced counts numeric if later formulas use them; joining them into the display text 3:5 changes their representation.

For measured decimals, choose and document a common unit first. Counts 4.8 and 7.2 expressed in tenths become integer counts 48 and 72. Passing 4.8 and 7.2 directly instead truncates to 4 and 7, whose GCD is one. Changing units deliberately is different from discarding fractional information.

For two positive integers, their GCD multiplied by their LCM equals their product:

=GCD(48,72)*LCM(48,72)
=48*72

Both have the expected result 3456, since the LCM is 144 and the GCD is 24. This is a useful small-number consistency control, not a promise about exact arithmetic for arbitrarily large values.

Decide whether the question asks for equal groups or repeated-cycle alignment. GCD solves the former; LCM solves the latter. A plausible numeric result can still answer the wrong question.

Check units, positive whole-number source values and whether all constraints are included. The zero-only case, negative entries, range text and extreme integers are not certified by these examples or the sparse official reference. Use a separate validation rule for business inputs rather than treating a computed divisor as proof that the data are valid.

• Google GCD help.
• Editorial testing standards.

Inputs are fictional. Approximate numerical answers are independently calculated mathematical expectations rounded to nine places, not captured native results. Complete coercion, extreme-magnitude and cross-client behavior remain untested.