AREAS Function in Apple Numbers: Syntax, Examples and Troubleshooting

AREAS helps audit whether a reference consists of one contiguous region or several separately listed regions. It is useful in complex analysis templates where a list of disjoint input blocks may change; for instance, reporting blocks from different sections of the same table. Empty-looking cells within a range do not turn that contiguous range into multiple areas: it is still one range reference.

If your actual goal is a cell count, row count, column count, or sum, choose a function designed for that quantity. AREAS only tells you how many distinct ranges were supplied. [Q1]

=AREAS(areas)

• areas (required): a reference consisting of a single range or a list of separate ranges.
• Single area: pass a range such as B2:B6; no extra grouping is required.
• Multiple areas: Apple says to separate referenced ranges with commas inside an additional pair of parentheses, for example =AREAS((B2:B6,D2:D6)). Omitting the extra parentheses changes the argument structure and is not the syntax Apple documents for a range list.
• Optional arguments/defaults: none documented. Supply the required areas argument. [Q1]

In locales whose decimal separator is a comma, Apple instructs you to use semicolons as function argument separators. The exact localized punctuation for a nested list of non-contiguous references has not been natively validated here. Select the ranges using Numbers’ function editor rather than guessing an equivalent multirange punctuation sequence. A single range such as =AREAS(A1:A5) has no comma-separated arguments to adapt. [L1]

Documentation version/platform: This tutorial uses Apple’s Formulas and Functions Help 15.4, accessed 2026-10-12. Being listed in this version does not certify historical release support on every Apple platform. No native Numbers execution has been performed.

Set up one table named Sections with at least eighteen rows and eight columns, using ordinary headers in row 1. Fill some cells (content is not used to calculate the count). Enter each formula in its own result cell:

For the second example, ensure your test table has at least 18 rows. The third example uses three distinct horizontal/square blocks. The listed outputs are directly documented by Apple, not native test observations. [Q1]

Why the answer is not the number of cells: A1:F8 contains many cell positions yet is one contiguous reference, so the answer is one. A1:F8 and A10:F18 are separate references, so the answer is two whether those cells contain numbers, text or blank values.

Imagine three summary regions: B2:B6, D2:D6, and F2:F6. Use:

=AREAS((B2:B6,D2:D6,F2:F6))

Expected result: 3. It counts three range expressions. This is an independent structural check applying Apple’s documented rule, not a native execution. You could use this number to double-check how many source regions are intended to feed a separately constructed reporting formula. It does not count rows or sum values within any of the regions.

Now compare:

=AREAS(B2:F6)

Expected result: 1. That single contiguous region spans the columns between the three blocks, but it is still supplied as one reference. These examples show why a discontiguous list of separate references is different from one wide rectangular range.

1. Returned 1 when you expected several areas: You may have entered one rectangular range, such as B2:F6, instead of several explicitly grouped ranges. Check the parentheses and each comma between referenced ranges. [Q1]
2. Function arguments rejected: For multiple ranges, Apple’s examples have two opening parentheses after AREAS, as in AREAS((A1:A3,C1:C3)). The outer pair belongs to the function call; the inner pair groups the list of ranges. [Q1]
3. Used references from another table: Confirm the actual table names, syntax and context using Numbers’ reference picker; do not import Excel’s ! sheet syntax unchanged.
4. Expecting AREAS to count nonblank cells: It does not inspect cell content for a count. A blank cell inside A1:A5 does not split that referenced range. Use a counting function for values, with correct type semantics. [Q1]
5. Locale uses semicolon separators: Apple documents the general rule, but the exact nested multi-area punctuation for every locale was not executed in Numbers. Verify with the locale-specific function editor. [L1]
6. Names, unions and intersection operators: Their representation can differ between spreadsheet applications and versions. This guide is confined to Apple’s documented single-range and parenthesized multirange examples; it does not claim that all Excel unions or defined-name behaviours transfer to Numbers.
7. An empty or invalid argument: The function requires an areas reference; a missing or malformed one does not meet the official syntax. The exact error code in every release has not been verified natively. [Q1]

Numbers: Apple’s syntax uses an extra grouping pair for multiple ranges, and the official examples demonstrate exactly how the count changes. Excel: also offers AREAS for counting distinct reference regions, but workbook/sheet references, noncontiguous unions and regional separators may differ. For other spreadsheet software, confirm the function exists and compare the official argument format. Do not assume every Excel-style union of ranges is accepted unchanged by Numbers. [Q1]

• COUNT in Apple Numbers — counts numeric cells instead of referenced regions.
• OFFSET in Apple Numbers — creates references based on an offset and dimensions.
• INDIRECT in Apple Numbers — interprets an address string as a reference.

• [Q1] Apple, “AREAS,” Functions Help 15.4: https://support.apple.com/guide/functions/areas-ffa59d8b61/15.4/web/1.0 — one required argument, grouped list of ranges, three official formula/output pairs, distinction between one and multiple ranges. Documentation checked, accessed 2026-10-12.
• [L1] Apple, “Functions overview,” Functions Help 15.4: https://support.apple.com/guide/functions/functions-overview-ffa083bef0c/15.4/web/1.0 — general locale separator rule. Documentation checked, accessed 2026-10-12.
• Validation: three Apple example outputs are documentation checked; the discontiguous-versus-rectangular examples were independently reasoned. Native execution: 0,