GESTEP
Supported, behaves as documentedCategory: Engineering · Last tested 2026-09-01
Real compatibility results for the GESTEP function: executed in Excel for the web, Google Sheets and LibreOffice Calc, with desktop Excel behavior from Microsoft’s official documentation (we do not run desktop Excel — Excel for the web is a different application and is executed separately). Syntax and links to that documentation are below.
Support matrix
| Engine | Documented | Live-tested | Verdict |
|---|---|---|---|
| Excel (desktop) | Yes | No — documented only | n/a |
| Excel for the web | — | Yes (recalc, 2026-09-01) | Supported, behaves as documented |
| Google Sheets | Yes | Yes (Drive import, 2026-08-31) | Supported, behaves as documented |
| LibreOffice Calc | Yes | Yes (25.8.7.3, 2026-08-31) | Supported, behaves as documented |
LibreOffice version history
We executed the same test cases under each LibreOffice release to show exactly when GESTEP’s support changed — not documentation claims, real results.
| LibreOffice version | Verdict | Tested |
|---|---|---|
| 24.2.0.3 | Supported, behaves as documented | 2026-08-31 |
| 24.8.7.2 | Supported, behaves as documented | 2026-08-31 |
| 25.2.0.3 | Supported, behaves as documented | 2026-08-31 |
| 25.8.7.3 | Supported, behaves as documented | 2026-08-31 |
Executed test cases
Excel for the web (executed 2026-09-01 via OneDrive recalculation)
These values come from Excel for the web, not from desktop Excel. They are two different implementations of the calculation engine, and this run measured only the web one: the corpus was uploaded to OneDrive as .xlsx, recalculated by Excel for the web on open, and downloaded again for readback. Excel for the web is a rolling service with no pinnable version, so the run is identified by its date. Where a value here disagrees with the Expected column — which is Microsoft’s documentation of the desktop product — we cannot tell you whether the web engine diverges from the desktop one or the documentation is wrong about both, because we do not run desktop Excel.
| Formula | Description | Result | Expected | Verdict |
|---|---|---|---|---|
| =GESTEP(5,4) | Microsoft's first worked example: 5 is greater than or equal to the step 4 | 1 | 1ProvenanceMicrosoft publishes '=GESTEP(5, 4)' with the result 1. Derived from the documented rule: "Returns 1 if number >= step; returns 0 (zero) otherwise." 5 >= 4. |
Matched |
| =GESTEP(5,5) | Microsoft's second worked example: the boundary, where number equals step | 1 | 1ProvenanceMicrosoft publishes '=GESTEP(5, 5)' with the result 1. This is the case that makes the comparison >= rather than >, and it is the one an implementation is most likely to get wrong; the page's own description of this example says "Checks whether 5 is greater than or equal to the step value, 5." |
Matched |
| =GESTEP(-4,-5) | Microsoft's third worked example: both arguments negative | 1 | 1ProvenanceMicrosoft publishes '=GESTEP(-4, -5)' with the result 1. -4 >= -5, so the answer is 1 -- a case an engine comparing magnitudes rather than signed values would get wrong, since |-4| < |-5|. |
Matched |
| =GESTEP(-1) | Microsoft's fourth worked example: step omitted, so it defaults to zero | 0 | 0ProvenanceMicrosoft publishes '=GESTEP(-1)' with the result 0, and documents "Step Optional. The threshold value. If you omit a value for step, GESTEP uses zero." -1 >= 0 is false. (The page's description of this example reads "Checks whether -1 is greater than the default step value, 0", dropping the "or equal to"; the syntax section's "Returns 1 if number >= step" is the rule relied on here, and both readings agree on this input.) |
Matched |
| =GESTEP(0) | Zero against the default step of zero, where the >= boundary and the default meet | 1 | 1ProvenanceNot published; derived from the two documented clauses together -- "Returns 1 if number >= step" and "If you omit a value for step, GESTEP uses zero" -- which give 0 >= 0, hence 1. Included because it is the single input that fails if EITHER the default is wrong OR the comparison is strict, and the published examples exercise those two rules only separately. |
Matched |
| =GESTEP("x",4) | A non-numeric argument | #VALUE! | #VALUE!ProvenanceExcel documents: "If any argument is nonnumeric, GESTEP returns the #VALUE! error value." |
Matched |
Google Sheets (executed 2026-08-31 via Drive import)
Google Sheets is a rolling service with no pinnable version, so this run is identified by its date. The corpus was imported to Drive as .xlsx, recalculated by Sheets, and exported back for readback.
| Formula | Description | Result | Expected | Verdict |
|---|---|---|---|---|
| =GESTEP(5,4) | Microsoft's first worked example: 5 is greater than or equal to the step 4 | 1 | 1ProvenanceMicrosoft publishes '=GESTEP(5, 4)' with the result 1. Derived from the documented rule: "Returns 1 if number >= step; returns 0 (zero) otherwise." 5 >= 4. |
Matched |
| =GESTEP(5,5) | Microsoft's second worked example: the boundary, where number equals step | 1 | 1ProvenanceMicrosoft publishes '=GESTEP(5, 5)' with the result 1. This is the case that makes the comparison >= rather than >, and it is the one an implementation is most likely to get wrong; the page's own description of this example says "Checks whether 5 is greater than or equal to the step value, 5." |
Matched |
| =GESTEP(-4,-5) | Microsoft's third worked example: both arguments negative | 1 | 1ProvenanceMicrosoft publishes '=GESTEP(-4, -5)' with the result 1. -4 >= -5, so the answer is 1 -- a case an engine comparing magnitudes rather than signed values would get wrong, since |-4| < |-5|. |
Matched |
| =GESTEP(-1) | Microsoft's fourth worked example: step omitted, so it defaults to zero | 0 | 0ProvenanceMicrosoft publishes '=GESTEP(-1)' with the result 0, and documents "Step Optional. The threshold value. If you omit a value for step, GESTEP uses zero." -1 >= 0 is false. (The page's description of this example reads "Checks whether -1 is greater than the default step value, 0", dropping the "or equal to"; the syntax section's "Returns 1 if number >= step" is the rule relied on here, and both readings agree on this input.) |
Matched |
| =GESTEP(0) | Zero against the default step of zero, where the >= boundary and the default meet | 1 | 1ProvenanceNot published; derived from the two documented clauses together -- "Returns 1 if number >= step" and "If you omit a value for step, GESTEP uses zero" -- which give 0 >= 0, hence 1. Included because it is the single input that fails if EITHER the default is wrong OR the comparison is strict, and the published examples exercise those two rules only separately. |
Matched |
| =GESTEP("x",4) | A non-numeric argument | #VALUE! | #VALUE!ProvenanceExcel documents: "If any argument is nonnumeric, GESTEP returns the #VALUE! error value." |
Matched |
LibreOffice Calc 25.8.7.3 (tested 2026-08-31)
| Formula | Description | Result | Expected | Verdict |
|---|---|---|---|---|
| =GESTEP(5,4) | Microsoft's first worked example: 5 is greater than or equal to the step 4 | 1 | 1ProvenanceMicrosoft publishes '=GESTEP(5, 4)' with the result 1. Derived from the documented rule: "Returns 1 if number >= step; returns 0 (zero) otherwise." 5 >= 4. |
Matched |
| =GESTEP(5,5) | Microsoft's second worked example: the boundary, where number equals step | 1 | 1ProvenanceMicrosoft publishes '=GESTEP(5, 5)' with the result 1. This is the case that makes the comparison >= rather than >, and it is the one an implementation is most likely to get wrong; the page's own description of this example says "Checks whether 5 is greater than or equal to the step value, 5." |
Matched |
| =GESTEP(-4,-5) | Microsoft's third worked example: both arguments negative | 1 | 1ProvenanceMicrosoft publishes '=GESTEP(-4, -5)' with the result 1. -4 >= -5, so the answer is 1 -- a case an engine comparing magnitudes rather than signed values would get wrong, since |-4| < |-5|. |
Matched |
| =GESTEP(-1) | Microsoft's fourth worked example: step omitted, so it defaults to zero | 0 | 0ProvenanceMicrosoft publishes '=GESTEP(-1)' with the result 0, and documents "Step Optional. The threshold value. If you omit a value for step, GESTEP uses zero." -1 >= 0 is false. (The page's description of this example reads "Checks whether -1 is greater than the default step value, 0", dropping the "or equal to"; the syntax section's "Returns 1 if number >= step" is the rule relied on here, and both readings agree on this input.) |
Matched |
| =GESTEP(0) | Zero against the default step of zero, where the >= boundary and the default meet | 1 | 1ProvenanceNot published; derived from the two documented clauses together -- "Returns 1 if number >= step" and "If you omit a value for step, GESTEP uses zero" -- which give 0 >= 0, hence 1. Included because it is the single input that fails if EITHER the default is wrong OR the comparison is strict, and the published examples exercise those two rules only separately. |
Matched |
| =GESTEP("x",4) | A non-numeric argument | #VALUE! | #VALUE!ProvenanceExcel documents: "If any argument is nonnumeric, GESTEP returns the #VALUE! error value." |
Matched |
Docs & syntax
- Excel (desktop): official documentation
- Google Sheets: official documentation
- LibreOffice Calc: official documentation