XPENG OTA
From Beta to Release
Published: 20.01.2026 – XPENG Guru Team
When XPENG releases an OTA (Over-The-Air) update, it follows a relatively structured — but not rigid — process. The objective is to ensure high quality, traffic safety, and software stability, even if this means that beta periods may be extended in certain cases.
Below is a simplified overview of the typical OTA timeline, which XPENG has approved for sharing as a reference.
Typical OTA Release Cycle at XPENG (Example)
| Phase | Stage | Typical Time Interval | Total Elapsed Time |
|---|---|---|---|
| 1 | Internal Beta (6901) | Start | – |
| 2 | Public Beta 1 (8901) | + approx. 1½ weeks | approx. 1½ weeks |
| 3 | Public Beta 2 (8902) | + approx. 1½ weeks | approx. 3weeks |
| 4 | Public Beta 3 (8903) | + approx. 1½ weeks | approx. 4½ weeks |
| 5 | Public Beta – Release Candidate (8904) | + approx. 1 weeks | approx. 5½ weeks |
| 6 | Officiel Release (8905) | + approx. 2 weeks | approx. 7½ weeks |
Important: The timeframes are indicative. The actual release date may be adjusted over time depending on test results and operational factors.
Not all releases go through four public beta phases. This can vary depending on the scope of features and the amount of feedback received during testing.
Why is the timeline flexible?
XPENG deliberately operates without a rigid, fixed OTA schedule. Adjustments may occur for several reasons, including:
- Bug fix considerations
Critical issues may require extended beta phases. - Feedback from beta users (VOC)
Real-world user feedback is highly valued and may influence both content and timing. - Holidays and operational factors
For example, Chinese public holidays or internal resource considerations. - Planned update content
Larger functional changes often require longer testing and validation periods.
Based on feedback — including input from our meetings in Guangzhou — the beta period from version 5.8.7 onward has been deliberately extended between each phase to allow more time for fixes and adjustments prior to final release.
Does a longer beta period affect the number of OTA releases?
The short answer is: No.
A longer beta cycle does not reduce the number of OTA releases within a calendar year. Instead, the overall release pace depends on factors such as:
- the complexity of the update content
- the number of new features
- user feedback (VOC)
- internal resource allocation at XPENG
Overall, the process reflects an effort to balance quality, feedback, and timing in OTA rollouts.
Here you will find an overview of the various releases XPENG has delivered since entering the Danish market: XOS Software.