COLUMNS in Calligra Sheets: Count Columns in a Cell Range

COLUMNS returns the number of columns spanned by a reference, including blank cells. A simple example is COLUMNS(A1:C3), expected to return 3. Use COLUMNS to determine a range width regardless of whether the included cells contain data. Use COLUMN to retrieve a column index.

When to use it: audit the size and location of imported tables, calculate an inclusive span, create structure-aware formulas, or check that references point to the intended part of a sheet. These calculations use cell positions, not cell contents.

=COLUMNS(reference)

Argument and defaults: Exactly one required reference/range argument. The pinned registry enables reference/array input and requires one argument; there is no omitted-reference default. The official help displays the literal syntax COLUMNS(reference); the release registry is authoritative for whether that displayed parameter can be omitted. reference here is a cell/range reference, such as A1:C3, not a promise that the literal quoted text "A1:C3" will be resolved as a reference. Although the official XML marks the parameter’s input type as String, the pinned C++ implementation uses parsed reference-region coordinates. Do not confuse UI parameter metadata with guarantees about quoted-string evaluation.

Version/source: The checked registry and implementation are from Calligra 26.08.2, released 2026-10-08, pinned at commit 72123cc643f6625351139e7df294544255a1056f. The English stable-KF6 KDE handbook and matching release XML/source were checked on 2026-10-11. The handbook is not a live test of all installations, languages, extensions or downstream Linux builds. Registry presence proves a function is registered in shipped source, not that a particular package loaded the module or that all edge cases behave identically.

Source-specific proof: reference.cpp lines 69–73 (setParamCount(1), setAcceptArray(), setNeedsExtra(true)) and implementation lines 319–329. The release-pinned help XML uses reference.xml lines 114–128.

Locale and formula entry: Start with = in a formula cell. All primary examples below contain only one argument, so they avoid separator ambiguity. The KDE English handbook uses semicolons to separate multiple arguments in other functions; your installation may display localized function names or separators. Reference notation can also vary with sheet settings. Use a genuine range reference rather than a typed text string.

1. Open a blank Calligra Sheets sheet. You may leave all the input referenced cells empty; the coordinate calculation does not depend on their stored values.
2. Enter the following formulas one per cell into H2:H7 (the H column is just a convenient results area). You do not need to type the reference strings into a separate column; each formula contains its own actual reference.
3. Observe the resulting values and compare with the independently calculated expectations below. They are expected outputs, not observed results from a native Calligra 26.08.2 session.

How these examples were checked: An independent Python reference-coordinate evaluator parsed ordinary A1 addresses and rectangular A1:C3 addresses, converted column letters to base-26 indices, and computed start/end coordinate differences inclusively. The expected results were compared with the published KDE examples and the pinned C++ branches. No native Calligra Sheets execution was performed.

Count the cells in a rectangular block

Formula: =COLUMNS(B2:F6)*ROWS(B2:F6). Expected result: 25. Five columns multiplied by five rows gives 25 cell positions, whether filled or blank.

Single-column range is still one column

Formula: =COLUMNS(A1:A100). Expected result: 1. The 100 rows do not change the column count.

Check inclusive endpoints

Formula: =COLUMNS(Z1:AB1). Expected result: 3. The named columns are Z, AA, and AB—not merely two columns because there are two endpoints.

Compare a block width with one cell

Formula: =COLUMNS(D2). Expected result: 1. COLUMNS counts the width of a reference; it does not return the cell’s column index 4.

Do ranges need values in every cell?

No. The checked code operates on the coordinates of a reference/range. The result reflects the reference geometry, not how many cells in it are nonempty. For counting populated values, investigate functions such as COUNT or COUNTA instead, with their own data-type rules. The links in this paragraph point to KDE’s official function chapter.

This function requires one reference argument. An empty call =COLUMNS() is not within the documented/registered signature; do not invent a numeric default.

• A cell value is not its position. =COLUMNS(A1:C3) describes a location; it does not read the cell’s visible number as a dimension/index. These examples remain meaningful when their targets are empty.
• Reference text is not necessarily a reference. Avoid replacing A1:C3 with "A1:C3". The XML’s parameter classification should not be interpreted as documented runtime support for quoted strings. Use direct reference syntax.
• Ranges include the start and end. For a rectangular span, calculate the coordinate difference plus one—not merely the difference.
• A discontiguous union, named range, imported structured reference or array constant may follow different parser rules. No native results for such cases were obtained, so this guide does not promise equivalence to Excel’s support for those forms.
• Broken references and syntax errors: check = and paired parentheses, the worksheet’s actual reference notation, and that the reference is a valid single rectangular region. The source returns Value::errorVALUE() when range boundary coordinates are invalid (col1 or col2 equals −1). It does not prove how a specific user-facing parser error is displayed.
• Numbers appear incorrect or truncated: ensure cells are formatted as numbers and the output column is wide enough. A different result from a current install should be recorded with the software version, package source, locale and formula—checked against these documented expectations.

Microsoft Excel: Excel documents COLUMNS(array) and accepts references or array formulas/constants. Calligra’s pinned implementation uses the reference-region boundaries to determine the width. A range like C1:E4 has three columns in both; do not promise identical behavior for Excel-specific array constants or spilled arrays. This comparison is grounded in the linked vendor documentation, not side-by-side execution. Excel documentation may use commas where KDE’s English help uses semicolons in multi-argument examples; a function with a single argument does not exercise that distinction.

LibreOffice Calc / Google Sheets: familiar function names exist, but cross-version parser details, array/spill behavior and error handling were not independently executed in this batch. Test workbook-specific edge cases in each application before migration; avoid assuming an Excel-only dynamic array example will behave the same in Calligra.

Alternate names: The Calligra 26.08.2 release registry gives COLUMNS no registered alternate names.

For a position instead of a width/height, use COLUMN or ROW; for a count of positions instead of a single index, use COLUMNS or ROWS. See KDE’s related reference entries: COLUMN; ROWS. Both the link destinations and the #COLUMNS anchor are in the checked English KDE chapter.

• Official KDE handbook: COLUMNS — published purpose, syntax and examples, consulted 2026-10-11.
• Pinned Calligra 26.08.2 reference function registration — official registry parameter count and module configuration, consulted 2026-10-11.
• Pinned Calligra 26.08.2 C++ implementation — coordinate calculation and invalid-coordinate branch, consulted 2026-10-11.
• Pinned Calligra 26.08.2 reference.xml — official English help text and related-function names, consulted 2026-10-11.
• KDE Gear 26.08.2 release announcement — release date, consulted 2026-10-11.
• Microsoft Excel documentation for COLUMNS — cross-software signature and behavior context, consulted 2026-10-11.

Native Calligra execution: not performed. Reference geometry and examples were checked against documentation, pinned source and independent calculations.