Baidu Open-Sources ERNIE 5.5 Flash Base: A 280B MoE Model Breakdown

Baidu open-sources ERNIE 5.5 Flash Base, a 280B sparse MoE base model with 14B activated parameters, released without post-training.
Baidu has released ERNIE 5.5 Flash Base, a sparse MoE foundation model with 280B total parameters, 14B activated parameters, and 33.5T training tokens. It was released directly after pre-training without mid-training or post-training, making it a native base model. Its value lies in reproducibility and customizability for SFT, RLHF, or domain-specific continued pre-training. The low-activation design supports 280B capacity at roughly 14B dense-level compute. Public details on architecture, benchmarks, and licensing remain limited.
Baidu has recently released ERNIE 5.5 Flash Base, a sparse MoE (Mixture-of-Experts) foundation model with 280B total parameters, 14B activated parameters, and 33.5T tokens of training data. One detail worth noting: the model was released directly after completing pre-training, without any mid-training or post-training — an approach that is uncommon in today's LLM release cadence, where instruction fine-tuning and RLHF are often touted as selling points.

What an "Unprocessed" Foundation Model Means
The Value of a Foundation Model Isn't in Conversational Ability
ERNIE 5.5 Flash Base has a very clear positioning: it is a base model, not a conversational product aimed directly at end users. According to the release information, the model was made public immediately after completing pre-training on 33.5T tokens, without going through mid-training or post-training stages.
For researchers, the value of such a "native" foundation model lies in reproducibility and customizability. Post-training introduces complex factors such as alignment preferences and instruction formats, making it difficult for downstream teams to determine whether a model's capabilities come from pre-training itself or from fine-tuning strategies. Releasing base weights directly is equivalent to handing over the results of the pre-training stage as-is, making it convenient for academic institutions and enterprises to conduct their own SFT, RLHF, or domain-specific continued pre-training on top of it.
Mid-training and post-training are umbrella terms for two different stages in the current LLM training pipeline. Mid-training typically refers to continued pre-training conducted after pre-training but before post-training, using higher-quality or domain-specific data (such as code, math, or long-form text) to further improve foundational capabilities, and sometimes also includes context length extension. Post-training covers supervised fine-tuning (SFT), reinforcement learning from human feedback (RLHF), direct preference optimization (DPO), and other steps, with the goal of teaching the model to follow instructions, align with human preferences, and develop conversational abilities.
Therefore, "without mid-training or post-training" means the model has only completed the foundational objective of next-token prediction, and its output is closer to a natural continuation of the input rather than an answer to a question. This also explains why base models perform poorly in conversational scenarios yet remain an ideal starting point for studying pre-training scaling laws and downstream fine-tuning methods.
The Significance of MoE Architecture and Activated Parameters
The configuration of 280B total parameters and 14B activated parameters is a typical sparse MoE design, with activated parameters accounting for a relatively small proportion of total parameters. During inference, only some experts are activated, meaning the actual computational cost is closer to that of a 14B-class dense model, while model capacity is supported by 280B parameters. This "large capacity, low activation" trade-off is one of the mainstream approaches today for improving model capability density and controlling inference costs.
The core mechanism of sparse MoE (Mixture-of-Experts) is to use a router/gating network to select a small number of expert sub-networks for each token to participate in computation, while the remaining experts stay silent. Therefore, during both training and inference, only the selected experts produce forward computation — the parameter count is large, but the per-pass computation is small.
This brings two direct consequences: first, the total parameter count determines the capacity ceiling and can accommodate more knowledge; second, the activated parameter count determines the FLOPs of a single forward pass, directly affecting latency and throughput. Note, however, that MoE's actual memory footprint does not decrease proportionally with a smaller activation ratio — all expert weights must reside in memory (or require complex expert parallelism and offloading strategies), so memory costs often fall between those of the activated parameters and the total parameters. This is precisely why MoE deployment is more complex than a dense model with the same activation count.
Data Scale and Release Cadence
The 33.5T-token pre-training data volume reflects the sustained investment in data scale by current leading vendors. Larger token budgets are usually associated with stronger general capabilities, but they also impose higher demands on training stability, data quality, and compute scheduling.
Releasing LLM base weights rather than only providing an API is itself an ecosystem strategy. It lowers the barrier to entry for external teams and makes the model easier to integrate into open-source toolchains and research workflows.
Token budget refers to the total number of tokens the model actually processes during pre-training, and is one of the key metrics for measuring training scale. Industry experience shows that with a fixed parameter count, increasing the token budget typically continues to reduce validation loss, but with diminishing returns; at the same time, the compute and data processing costs required for training rise accordingly. 33.5T tokens represents a relatively high level among current leading models, which means the training process requires a stable data supply pipeline, deduplication and quality filtering mechanisms, and the ability to monitor and recover from training instability (such as loss spikes). The ratio of tokens to parameters (tokens per parameter) is also a commonly used reference for judging whether a model is "sufficiently trained."
Industry Observation: Parallel Open-Source and Closed-Source Routes
Baidu operates both closed-source API products and open-weight models, and the release of ERNIE 5.5 Flash Base continues this parallel approach. Against the backdrop of intensifying LLM competition at home and abroad, open-source base models serve as both a technical showcase and a means of attracting developers and expanding ecosystem influence.
As a side note, the information in this release is fairly limited — the available details focus on parameter scale, activated parameters, training token count, and the "no post-training" release format. There is no further public information on architecture details, evaluation results, or license terms. For teams planning to actually use the model, it is advisable to refer to the official model card and license agreement.

FAQ
Can ERNIE 5.5 Flash Base be used directly for conversation? It is a foundation model without post-training, so it lacks instruction-following and conversational alignment capabilities. It typically requires downstream fine-tuning before it can be used for conversational applications.
Do 14B activated parameters mean inference costs are comparable to a 14B dense model? The activated computation of sparse MoE is close to that order of magnitude, but actual inference costs are also affected by expert routing, memory footprint, and batching strategies, so they cannot be simply equated.
One-line Summary
Baidu releases ERNIE 5.5 Flash Base, a 280B sparse MoE foundation model with 14B activated parameters, open-sourced without post-training.
Paragraph Summary
Baidu has released ERNIE 5.5 Flash Base, a sparse MoE foundation model with 280B total parameters and 14B activated parameters, trained on 33.5T tokens. Its most notable feature is that it was released directly after pre-training, without mid-training or post-training, making it a native base model. The article notes that the value of such models lies not in conversational ability but in reproducibility and customizability, enabling researchers and enterprises to conduct their own SFT, RLHF, or domain-specific continued pre-training. The low activated-parameter design aims to support 280B parameter capacity with computational overhead close to a 14B dense model, controlling inference costs and improving capability density. Releasing base weights also continues Baidu's parallel ecosystem strategy of closed-source APIs and open weights. The article also cautions that public information is limited this time, with architecture details, evaluation results, and license terms undisclosed, and that actual use should be governed by the official model card and license agreement.
Related articles

AI Coding Enters the Team Collaboration Era: Interpreting Three Major Moves from Meta, GitHub, and Mistral
Meta acquires Conductor, GitHub Copilot Fusion becomes available, Mistral opens Large 4 weights—three moves show AI coding shifting from code generation to organizing development workflows. This article explains task orchestration, model collaboration, and cost control for developers.

Building a RAG Assistant with Dify: A Practical Guide to Knowledge Bases, Workflows, and Agent Nodes
How should knowledge bases, workflows, and Agent nodes connect in a Dify RAG assistant? We break down the division of labor and wiring logic for a shippable app.
Tech FrontiersThe AI Industry Doesn't Lack Marketing—It Lacks Good Products
AI faces market selloffs and public skepticism—is marketing really the problem? This analysis of market signals and product experience argues the core困境 is incomplete products and a gap between promises and experience; the only way to change perceptions is to ship better products.