XPENG OTA
How OTA updates reach Europe - beta phases, installation, and what to expect.
Last reviewed: June 2026
XPENG OTA (Over-The-Air) delivers infotainment and vehicle software updates without a workshop visit. This guide explains how XPENG rolls out updates internationally, what owners should expect, and how to install updates on your car. Part of the Guides collection under Software.
What is XPENG OTA?
When XPENG ships an OTA package, it follows a relatively fixed - but not rigid - process. The goal is high quality, road safety, and stable software, even when that means extending beta periods. Updates reach your vehicle through the mobile app and in-car About → Update settings flow (see also XOS Settings for automatic OTA toggles).
From beta to public release
Before a build reaches all owners, XPENG typically moves it through internal and public beta stages. The diagram below is a simplified view of the pipeline XPENG has shared as a reference for international markets.
Diagram: XPENG
Typical OTA timeline (example)
Below is a simplified schedule for a major XOS release with four public beta waves. Not every version uses all phases - scope and feedback can shorten or skip steps.
| Phase | Label | Typical gap | Cumulative |
|---|---|---|---|
| 1 | Internal Beta (6901) | Start | - |
| 2 | Public Beta 1 (8901) | + ~1½ weeks | ~1½ weeks |
| 3 | Public Beta 2 (8902) | + ~1½ weeks | ~3 weeks |
| 4 | Public Beta 3 (8903) | + ~1½ weeks | ~4½ weeks |
| 5 | Public Beta - Release Candidate (8904) | + ~1 week | ~5½ weeks |
| 6 | Official Release (8905) | + ~2 weeks | ~7½ weeks |
Important: Timings are indicative only. The actual release date can shift based on test results and operational constraints. Some releases do not run four public betas - it depends on feature scope and feedback volume.
Why is the schedule flexible?
XPENG deliberately avoids a locked annual OTA calendar. Adjustments happen for several reasons:
- Critical bugfixes - serious defects can extend beta phases before wide rollout.
- Beta user feedback (VOC) - real-world reports influence both content and timing.
- Holidays and operations - e.g. Chinese public holidays or internal resource planning.
- Scope of the update - larger functional changes need longer validation.
From XOS 5.8.7 onward, XPENG lengthened gaps between beta phases (partly based on owner feedback from Guangzhou meetings) to allow more fixes before general release.
Does a longer beta mean fewer OTAs per year?
No. A longer beta cycle does not reduce how many OTAs XPENG can ship in a calendar year. Overall release pace depends on complexity, new feature volume, VOC feedback, and internal resourcing - not beta length alone.
The process balances quality, owner feedback, and timing - beta time buys stability rather than replacing other releases.
Installing updates on your car
Once a build is released to your region and VIN cohort, installation is owner-controlled:
- Notification - the mobile app and/or infotainment prompt when a package is available.
- Download - usually while parked; connecting the car to Wi‑Fi (see Connections in XOS Settings) can speed large downloads.
- Schedule or install now - choose a convenient time; the car must meet preconditions (sufficient charge, parked, sometimes gear in P).
- Automatic updates - enable About → Update settings → Automatic upgrade if you want eligible packages to install without manual confirmation (still subject to safety checks).
During installation the vehicle may be temporarily unavailable. Plan updates overnight or before a trip when you do not need remote app access.
Troubleshooting
- Download slow or stuck - move the car within Wi‑Fi range, keep it awake (but parked), and retry from the update screen. Newer XOS builds have improved Wi‑Fi download reliability.
- Install prerequisites not met - check battery level, parking brake, and that no other service session is active; messages on screen usually state the blocker.
- Update failed mid-install - do not drive if the car reports an incomplete update; retry when prompted or contact XPENG service. Recent releases explicitly target OTA failure recovery and stability.
- On beta builds - public beta versions (890x) are pre-release; report issues through official beta channels rather than expecting dealer-level support for every edge case.
Release notes & software hub
Track what each version changes on the XOS Releases hub - release notes, version history, and the article grid for XOS topics. Example entry: XOS 4.4.1 release notes.
Parent hub: Software · Related: XOS Settings · XCOMBO