Google’s Free Cash Flow Will Hit Zero Next Year
Key Takeaways
- •Alphabet capex 2026 forecast $175‑185 bn, near‑matching operating cash.
- •Free cash flow could drop to zero, compressing EV/FCF ratio.
- •Peers Amazon, Meta, Microsoft also ramping AI‑related capex dramatically.
- •Cloud revenue up 48% YoY, showing growth despite cash burn.
- •Success hinges on AI infrastructure returns outweighing massive spending.
Pulse Analysis
Alphabet’s capital‑expenditure outlook signals a strategic pivot from cash generation to infrastructure dominance. After a 74% YoY rise to $91.4 bn in 2025, the company now projects $175‑$185 bn for 2026, a level that would consume virtually all operating cash. This pattern mirrors Amazon’s 2025 free‑cash‑flow collapse after $131.8 bn of capex and reflects a broader industry shift where AI‑centric spending eclipses traditional profitability metrics.
The rationale behind the spending binge is the belief that AI infrastructure will become a winner‑take‑most market. Alphabet’s Google Cloud posted $17.7 bn in Q4 2025 revenue, up 48% YoY, and the segment now contributes a 31.6% operating margin at the Alphabet level. If these investments unlock comparable margins at scale, the temporary cash‑flow compression could be justified. However, the timing and magnitude of AI‑driven revenue upside remain uncertain, and investors must weigh the risk of over‑building against the potential for outsized returns.
For investors, the key question is valuation relevance. With free cash flow projected to hit zero, traditional EV/FCF multiples lose meaning, pushing analysts toward revenue‑based metrics and growth assumptions. The scenario underscores a broader market dilemma: whether to reward companies for aggressive, long‑term bets on AI or penalize them for short‑term cash erosion. The next earnings cycle will be a litmus test for whether Alphabet’s AI spend translates into sustainable earnings power or leaves the $1.7 trillion market cap vulnerable to a correction.
Google’s free cash flow will hit zero next year
Comments
Want to join the conversation?