Loading…

Synopsys (SNPS) backlog: remaining performance obligations

How much revenue Synopsys already has under contract, how fast it converts, and who it is with.

Data as of .

Synopsys backlog history

$0$5B$10BOct 2022Apr 2023Oct 2023Apr 2024Oct 2024Apr 2025Oct 2025Apr 2026Jul 2026Backlog (RPO)Trailing 12-month revenue
Remaining performance obligations at each quarter end (bars) against trailing twelve-month revenue (line).
Amounts in USD. Source: SEC XBRL filings.
Quarter endBacklog (RPO)TTM revenueCoverageCustomer prepayments
31 Jul 2026$10.9B$9.42B1.2 yrs$2.72B
30 Apr 2026$11.0B$8.68B1.3 yrs$2.81B
31 Jan 2026$11.3B$8.01B1.4 yrs$2.88B
31 Oct 2025$11.4B$7.05B1.6 yrs$2.63B
31 Jul 2025$10.1B$6.44B1.6 yrs$2.37B
30 Apr 2025$8.10B$6.22B1.3 yrs$1.71B
31 Jan 2025$7.70B$6.07B1.3 yrs$1.64B
31 Oct 2024$8.10B$6.13B1.3 yrs$1.73B
31 Jul 2024$7.90B$5.83B1.4 yrs$1.68B
30 Apr 2024$7.90B$5.66B1.4 yrs$1.77B
31 Jan 2024$8.20B$5.47B1.5 yrs$2.05B
31 Oct 2023$8.10B$5.32B1.5 yrs$1.71B

Questions

What is Synopsys's backlog?
Synopsys reported $10.9B of remaining performance obligations at 31 Jul 2026, up 8% from a year earlier and down 1% from the previous quarter. That is 1.2 years of trailing revenue already under contract. Book-to-bill last quarter: 0.96.
How fast does Synopsys's backlog turn into revenue?
Over the last twelve months Synopsys recognised revenue equal to about 86% of the backlog it started each quarter with.

About these numbers

Remaining performance obligations (RPO) are revenue a company has contracted but not yet recognised, as reported in its SEC filings (XBRL tag RevenueRemainingPerformanceObligation). Coverage = backlog ÷ trailing twelve-month revenue. Book-to-bill = (change in backlog + revenue) ÷ revenue. Conversion = revenue recognised ÷ the backlog at the start of each quarter, summed over four quarters. Counterparty values come from company filings and releases.