← All functions

IMARGUMENT

Supported, behaves as documented

Category: Engineering · Last tested 2026-09-01

Real compatibility results for the IMARGUMENT 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

EngineDocumentedLive-testedVerdict
Excel (desktop)Yes No — documented only n/a
Excel for the web— Yes (recalc, 2026-09-01) Supported, behaves as documented
Google SheetsYes Yes (Drive import, 2026-08-31) Supported, behaves as documented
LibreOffice CalcYes 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 IMARGUMENT’s support changed — not documentation claims, real results.

LibreOffice versionVerdictTested
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.

FormulaDescriptionResultExpectedVerdict
=ROUND(IMARGUMENT("3+4i"),12) Microsoft's documented worked example: the argument (theta) of 3+4i in radians 0.927295218002 0.927295218002
Provenance

Microsoft publishes '=IMARGUMENT("3+4i")' with the result 0.92729522. Derived independently with mpmath at 50 digits as atan2(4, 3) = 0.92729521800161223243, which rounds to exactly the published 0.92729522 at the 8 dp the page prints; asserted at 12 dp. Cross-check from a completely different direction: this same number is the imaginary part of Microsoft's own published IMLN("3+4i") result, 1.6094379124341+0.927295218001612i, since ln(z) = ln|z| + i*arg(z) -- two Microsoft pages independently agreeing on the same constant.

Matched
=ROUND(IMARGUMENT("1+i"),12) The argument of 1+i is pi/4 0.785398163397 0.785398163397
Provenance

Not published; derived from atan2(1, 1) = pi/4 = 0.78539816339744830962 (mpmath, 50 digits). Chosen because the answer is a recognizable closed form, so a wrong value is obviously wrong rather than merely different.

Matched
=ROUND(IMARGUMENT("-1"),12) The argument of -1 is pi, which is where a two-argument arctangent is required 3.14159265359 3.14159265359
Provenance

Derived from atan2(0, -1) = pi = 3.1415926535897932385. This is the case that distinguishes a correct implementation from one built on the single-argument arctangent of y/x: that shortcut computes atan(0/-1) = atan(0) = 0 and loses the quadrant entirely, returning 0 instead of pi. Microsoft's page states the relationship as tan(theta) = y/x, which is exactly the ambiguous form, so the quadrant convention has to be inferred from the published example (3+4i, first quadrant) plus the standard principal-value range -- and this case is what makes that inference testable.

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.

FormulaDescriptionResultExpectedVerdict
=ROUND(IMARGUMENT("3+4i"),12) Microsoft's documented worked example: the argument (theta) of 3+4i in radians 0.927295218 0.927295218002
Provenance

Microsoft publishes '=IMARGUMENT("3+4i")' with the result 0.92729522. Derived independently with mpmath at 50 digits as atan2(4, 3) = 0.92729521800161223243, which rounds to exactly the published 0.92729522 at the 8 dp the page prints; asserted at 12 dp. Cross-check from a completely different direction: this same number is the imaginary part of Microsoft's own published IMLN("3+4i") result, 1.6094379124341+0.927295218001612i, since ln(z) = ln|z| + i*arg(z) -- two Microsoft pages independently agreeing on the same constant.

Matched
=ROUND(IMARGUMENT("1+i"),12) The argument of 1+i is pi/4 0.7853981634 0.785398163397
Provenance

Not published; derived from atan2(1, 1) = pi/4 = 0.78539816339744830962 (mpmath, 50 digits). Chosen because the answer is a recognizable closed form, so a wrong value is obviously wrong rather than merely different.

Matched
=ROUND(IMARGUMENT("-1"),12) The argument of -1 is pi, which is where a two-argument arctangent is required 3.141592654 3.14159265359
Provenance

Derived from atan2(0, -1) = pi = 3.1415926535897932385. This is the case that distinguishes a correct implementation from one built on the single-argument arctangent of y/x: that shortcut computes atan(0/-1) = atan(0) = 0 and loses the quadrant entirely, returning 0 instead of pi. Microsoft's page states the relationship as tan(theta) = y/x, which is exactly the ambiguous form, so the quadrant convention has to be inferred from the published example (3+4i, first quadrant) plus the standard principal-value range -- and this case is what makes that inference testable.

Matched

LibreOffice Calc 25.8.7.3 (tested 2026-08-31)

FormulaDescriptionResultExpectedVerdict
=ROUND(IMARGUMENT("3+4i"),12) Microsoft's documented worked example: the argument (theta) of 3+4i in radians 0.927295218002 0.927295218002
Provenance

Microsoft publishes '=IMARGUMENT("3+4i")' with the result 0.92729522. Derived independently with mpmath at 50 digits as atan2(4, 3) = 0.92729521800161223243, which rounds to exactly the published 0.92729522 at the 8 dp the page prints; asserted at 12 dp. Cross-check from a completely different direction: this same number is the imaginary part of Microsoft's own published IMLN("3+4i") result, 1.6094379124341+0.927295218001612i, since ln(z) = ln|z| + i*arg(z) -- two Microsoft pages independently agreeing on the same constant.

Matched
=ROUND(IMARGUMENT("1+i"),12) The argument of 1+i is pi/4 0.785398163397 0.785398163397
Provenance

Not published; derived from atan2(1, 1) = pi/4 = 0.78539816339744830962 (mpmath, 50 digits). Chosen because the answer is a recognizable closed form, so a wrong value is obviously wrong rather than merely different.

Matched
=ROUND(IMARGUMENT("-1"),12) The argument of -1 is pi, which is where a two-argument arctangent is required 3.14159265359 3.14159265359
Provenance

Derived from atan2(0, -1) = pi = 3.1415926535897932385. This is the case that distinguishes a correct implementation from one built on the single-argument arctangent of y/x: that shortcut computes atan(0/-1) = atan(0) = 0 and loses the quadrant entirely, returning 0 instead of pi. Microsoft's page states the relationship as tan(theta) = y/x, which is exactly the ambiguous form, so the quadrant convention has to be inferred from the published example (3+4i, first quadrant) plus the standard principal-value range -- and this case is what makes that inference testable.

Matched

Docs & syntax