Skip to content

NVIDIA CORP: operating expenses

Operating expenses for NVIDIA CORP. Inspect selected reporting periods, original units and SEC filing links; download the financial history.

All NVIDIA CORP financial histories

What this measure means

Recurring operating costs under this accounting concept, generally excluding production costs included in cost of sales. Check filing presentation before combining expense subtotals.

Exact concept: us-gaap:OperatingExpenses. Each value covers an annual-duration reporting interval, shown with both start and end dates. Different units remain separate; no currency conversion or interpolation is applied.

Coverage of this history

Selected reporting periods run from 2007-01-29 to 2026-01-25. The SEC response was captured on 2026-09-19.

Selected filing history

Operating expenses in original reported units, latest-filed observation per period
Period startPeriod endValueUnitFiledSource filing
2025-01-272026-01-2523,076,000,000USD2026-02-2510-K · 0001045810-26-000021
2024-01-292025-01-2616,405,000,000USD2026-02-2510-K · 0001045810-26-000021
2023-01-302024-01-2811,329,000,000USD2026-02-2510-K · 0001045810-26-000021
2022-01-312023-01-2911,132,000,000USD2025-02-2610-K · 0001045810-25-000023
2021-02-012022-01-307,434,000,000USD2024-02-2110-K · 0001045810-24-000029
2020-01-272021-01-315,864,000,000USD2023-02-2410-K · 0001045810-23-000017
2019-01-282020-01-263,922,000,000USD2022-03-1810-K · 0001045810-22-000036
2018-01-292019-01-273,367,000,000USD2021-02-2610-K · 0001045810-21-000010
2017-01-302018-01-282,612,000,000USD2020-02-2010-K · 0001045810-20-000010
2016-02-012017-01-292,129,000,000USD2019-02-2110-K · 0001045810-19-000023
2015-01-262016-01-312,064,000,000USD2018-02-2810-K · 0001045810-18-000010
2014-01-272015-01-251,840,000,000USD2017-03-0110-K · 0001045810-17-000027
2013-01-282014-01-261,772,000,000USD2016-03-1710-K · 0001045810-16-000205
2012-01-302013-01-271,578,104,000USD2015-03-1210-K · 0001045810-15-000036
2011-01-312012-01-291,408,218,000USD2014-03-1310-K · 0001045810-14-000030
2010-02-012011-01-301,153,343,000USD2013-03-1210-K · 0001045810-13-000008
2009-01-262010-01-311,275,868,000USD2012-03-1310-K · 0001045810-12-000013
2008-01-282009-01-251,244,969,000USD2011-03-1610-K · 0001045810-11-000015
2007-01-292008-01-271,032,934,000USD2010-03-1810-K · 0001045810-10-000006

Related financial histories

Inspect the source

Entity
NVIDIA CORP / CIK 0001045810
Captured
2026-09-19T09:30:27.102Z
SEC response SHA-256
19ef503a5770f5660964b3c3aea6937579d9b359da344afe6a9adf59c63d26ff

Current SEC company facts · Download the original response snapshot (gzip) · Download the selected JSON

Latest-filed annual-report facts per unit and reporting period at capture time. Duration facts cover 300 to 400 days. This selection can include restatements and is not a point-in-time backtest dataset. Missing concepts are omitted, never zero-filled. Values retain original units and are not currency converted. Extended concepts require compatible unit shapes and at least three reporting ends with changing values within one unit. Constant or incompatible added histories are omitted.

Public company accounting reference, not market prices, returns, an investment recommendation, or ALPHAC performance. Validate a separately constructed return series with the validation API; accounting values are not returns.

Use this in research

A financial period ends before its results become public. Use the filing date as a minimum availability boundary, inspect amendments, and retain the original filing vintage when testing historical signals. This latest-filed selection can contain information unavailable at the time.

These pages do not supply prices, total-return histories, corporate-action adjustments or a tradable universe. Build those inputs separately before evaluating a strategy. A profitable backtest can still reflect selection bias or costs that were left out.

Research methodology · Execution and cost assumptions · Check backtest overfitting

Build with the open-source tools

Use these accounting records as inspectable inputs. When you have constructed a return series, the validation tools can help test its statistical evidence and preserve the result with its limitations.

Read the published dataset with Python
import json
from urllib.request import urlopen

with urlopen("https://canlicapital.com/company-data/0001045810.json") as response:
    record = json.load(response)
print(record["fetched_at"])
print(record["policy"])
for concept in record["concepts"]:
    print(concept["tag"], next(iter(concept["observations"])))