What Cars Use CHAdeMO? 2026 Compatibility & Site Planning Guide
Identify the exact vehicle and inlet first—then decide whether a real site should retain, share, add or retire CHAdeMO capacity.
Checked September 2026 · Reviewed by Marvin
Short answer: CHAdeMO appears most consistently on earlier Nissan LEAF and e-NV200 vehicles, Mitsubishi i-MiEV-family vehicles and selected Mitsubishi plug-in hybrids such as the Outlander PHEV. It also appears on some Kia Soul EV, Lexus UX300e and other Japan- or region-specific models. But a model name is not enough. Confirm the sales market, model year, trim and physical DC inlet before choosing a charger or promising a driver compatibility.
For a charging-site owner, the more important question is not “Can I find a list of CHAdeMO cars?” It is:
How many vehicles in my real catchment have a native CHAdeMO inlet, when do they need to charge, and what connector capacity should I preserve for them?
This guide answers both questions. The vehicle examples are a dated planning aid, not a substitute for the vehicle handbook, inlet inspection or an interoperability test.
The 30-second check: does this exact car use CHAdeMO?
Use this order:
- Identify the exact vehicle. Record manufacturer, model, model year, trim and original sales market. A grey import may not match the specification sold locally.
- Open the charge door and inspect the DC inlet. Compare the inlet geometry with the manufacturer handbook or charging label. Do not identify it from the AC inlet beside it.
- Confirm the charging specification. Check the vehicle handbook or OEM specification for the allowed DC connector and charging limit. Then match it to the charger’s fitted cable and tested protocol implementation.
The US Department of Energy describes CHAdeMO as one of the DC fast-charging connector systems and notes that the vehicle’s charge port determines which system it can use. That physical boundary is more reliable than a search snippet, marketplace listing or assumption based on the badge.
Four checks before a cable becomes a promise
→
→
→
CHAdeMO vehicle compatibility at a glance
The table deliberately uses categories instead of pretending to be a permanent worldwide catalogue.
| Vehicle group | Examples associated with CHAdeMO | Planning status in 2026 | What must be verified |
|---|---|---|---|
| High-volume installed fleet | Earlier-generation Nissan LEAF | Important legacy demand in many markets | Generation, model year, sales market, native DC inlet and vehicle charge limit |
| Nissan light commercial/legacy | Nissan e-NV200 and selected Japan-market Nissan EVs | Market-specific installed fleet | Import origin, year and inlet |
| Mitsubishi EV family | Mitsubishi i-MiEV, Minicab MiEV/EV and related derivatives | Mostly legacy or regional | Badge-sharing does not prove identical port specification |
| Mitsubishi PHEVs | Selected Outlander PHEV and Eclipse Cross PHEV versions | Still relevant in specific regions | Country, year, trim and whether rapid charging was fitted |
| Other historical passenger EVs | Earlier Kia Soul EV, Lexus UX300e, Peugeot iOn, Citroën C-Zero and selected derivatives | Legacy or market-dependent | Exact OEM specification; do not extrapolate across generations |
| Japan-market current/late examples | Nissan Sakura, Mitsubishi eK X EV and other Japan-market models shown in CHAdeMO Association material | Relevant mainly where these vehicles operate or are imported | Original market, import population and local support |
| Adapter-dependent vehicles | Certain Tesla vehicles with an approved, market-compatible CHAdeMO adapter | Not native CHAdeMO | Exact vehicle, adapter, firmware, market and power limit |
The CHAdeMO Association’s vehicle material includes many more examples, from compact cars to commercial vehicles. Some lists are historical; some represent Japan-only or adapter cases. Their value is to show the breadth of the installed base—not to prove that every version of every listed nameplate can use a cable at your site.
The Nissan LEAF needs a generation check
The LEAF created much of the worldwide CHAdeMO installed base. A Nissan UK brochure for the documented earlier LEAF specifies a 50 kW CHAdeMO rapid charger. That is solid evidence for that version, not permission to write “every LEAF uses CHAdeMO forever.”
New generations can change connector strategy, especially across North America, Europe and Japan. A site survey should record the inlet on the vehicles that actually visit. A used-car buyer should inspect the car and handbook rather than relying on a generic LEAF page.
Mitsubishi compatibility is market- and equipment-dependent
The i-MiEV family is a well-established CHAdeMO example. Selected Outlander PHEV and Eclipse Cross PHEV versions also use CHAdeMO rapid charging, but PHEV charging equipment can differ by country and trim. The presence of an AC charge inlet does not prove that the DC fast-charge inlet is fitted.
For fleets, request a vehicle schedule with VIN-linked or asset-linked inlet photographs. That small documentation step is cheaper than discovering after installation that a regional trim cannot use the planned cable.
Older Kia, Lexus, Peugeot and Citroën examples are not universal rules
Earlier Kia Soul EV, Lexus UX300e and Mitsubishi-derived European compact EVs appear in CHAdeMO Association material. Treat them as leads for verification. Later models carrying the same brand—and sometimes the same model family—may use CCS or another connector.
This is especially important in used-import markets across Africa, Asia, Latin America and island markets. The local vehicle population can differ sharply from the connector standard normally associated with the country.
Tesla is an adapter case, not a native CHAdeMO vehicle
Historical CHAdeMO material lists Tesla Model S with an adapter. An adapter-dependent path must be confirmed against the exact vehicle, destination-market hardware, firmware and adapter approval. It should not be the basis for claiming that all Tesla vehicles are CHAdeMO compatible.
The practical rule is simple: native inlet first; approved adapter path second; unsupported conversion claims never.
A matching plug does not guarantee useful charging performance
Connector compatibility only answers whether the vehicle and charger have a supported physical and communication path. Delivered power is bounded by several independent ceilings:
- the vehicle’s requested voltage and current;
- battery state of charge and temperature;
- the vehicle’s DC charging curve and protective limits;
- the charger’s voltage, current and thermal limits;
- cable rating and cooling design;
- site power allocation when outputs share a cabinet;
- environmental derating and active faults.
The CHAdeMO Association announced version 2.1 in 2026 with specifications reaching 800 A and theoretical power up to 800 kW under its stated configuration. That protocol capability does not make a legacy passenger vehicle an 800 kW vehicle. An older LEAF may request only a small fraction of the charger label, and its battery-management system remains in control of the session.
For procurement, ask for an operating envelope, not only a headline kW number. It should show usable voltage range, maximum cable current, continuous or derated behavior, connector option, simultaneous-output logic and the vehicle/test conditions behind any performance claim.
Make the installed fleet—not the headline—choose the bay
Should a charging site keep CHAdeMO in 2026?
There is no responsible universal yes-or-no answer. Use the installed fleet and operating objective.
Retain dedicated CHAdeMO capacity when
- session records show repeat CHAdeMO use;
- local taxis, municipal fleets, delivery vehicles or imported EVs depend on it;
- removing it would strand an identifiable customer group;
- the existing unit remains supportable, safe and interoperable;
- uptime and repair cost justify the bay.
Add or preserve a shared multi-standard position when
- demand exists but is too intermittent for a dedicated bay;
- a cabinet can serve separate CCS and CHAdeMO cables under clearly documented power-sharing rules;
- site geometry avoids one vehicle blocking both connector groups;
- the operator can communicate simultaneous-use restrictions accurately.
“Two cables” does not automatically mean “two cars can charge at full power.” The RFQ and acceptance test must state whether the outputs are alternative, simultaneous, sequential or dynamically shared.
Plan a managed retirement when
- authenticated sessions show sustained decline, not merely a low-use month;
- the affected drivers have practical nearby alternatives;
- parts, cable service or protocol support can no longer meet the uptime target;
- the bay can deliver materially more value for the site’s verified future fleet;
- transition communication and accessibility have been considered.
Do not remove a connector simply because new-car headlines have changed. NREL’s Q2 2024 US report estimated that native CHAdeMO vehicles were a small share of registered US BEVs, while also observing that CHAdeMO connector counts were still growing and older vehicles remained on the road. The correct 2026 decision requires newer local session data.
Build a vehicle census before writing the charger RFQ
For a private fleet, this is straightforward. For a public site, combine available evidence:
- Export 6–12 months of sessions by connector, time, duration, energy and failed-session code.
- Identify repeat users without storing unnecessary personal data.
- Review local registrations, fleet contracts, taxi composition and used-import patterns.
- Separate native CHAdeMO vehicles from adapter requests.
- Record peak concurrency, not just annual energy.
- Test whether one shared output would create queues during the actual arrival window.
A simple planning ratio is:
CHAdeMO peak service ratio = CHAdeMO sessions in the design peak ÷ total DC sessions in the design peak
Do not use that ratio alone. A low-volume connector may still be operationally critical for an ambulance support fleet, municipal vehicle or contracted taxi group. Add a service-criticality flag and a maximum acceptable wait.
What to put in a CHAdeMO charger RFQ
If the census supports CHAdeMO, make the option testable. Ask the supplier to state:
| RFQ field | Required answer |
|---|---|
| Destination | Country, installation environment and applicable compliance route |
| Vehicle schedule | Manufacturer, model, year, market, inlet photo and expected daily sessions |
| Connector configuration | Exact CHAdeMO cable assembly plus every other fitted connector |
| Electrical envelope | DC voltage range, maximum output current, rated power and relevant derating |
| Output behavior | Alternative, sequential, simultaneous or dynamic sharing; minimum guaranteed power where applicable |
| Protocol/software | Implemented CHAdeMO version, charger firmware baseline, CSMS/OCPP scope and remote diagnostics |
| Cable system | Length, current rating, cooling method if used, holster and replacement path |
| Evidence | Model-specific datasheet, conformity documents, FAT procedure and supported-vehicle test plan |
| Acceptance | Successful start, controlled ramp, stop, fault recovery, meter/log agreement and multi-output behavior |
| Lifecycle | Spare parts, cable lead time, firmware support, warranty boundary and field-service responsibility |
HG Power materials list CHAdeMO among configurable connector options for a documented mobile/battery-integrated family. That does not establish universal availability across the 40–480 kW portfolio. A correct quotation must identify the exact charger family and fitted connector, then attach the applicable technical and compliance evidence.
How to test compatibility before rollout
A connector option on a datasheet is the beginning of verification, not the end.
Use a representative vehicle set and record:
- charger model, serial number and firmware;
- cable/connector identity;
- vehicle model, year, market and battery condition;
- starting state of charge and battery temperature where available;
- handshake and authorization result;
- requested versus delivered voltage/current over the session;
- stop behavior from vehicle, charger and emergency path;
- fault codes and recovery behavior;
- transaction record received by the CSMS;
- behavior when another output starts or stops.
For a public mixed-fleet site, one successful LEAF session does not prove every legacy CHAdeMO vehicle will behave identically. Define the representative set from the real vehicle census and keep the test record with the commissioning package.
CHAdeMO, CCS and J3400 can coexist—but every cable needs a job
Mixed connector sites are often sensible during a fleet transition. The risk is buying cables by logo count instead of service demand.
- CHAdeMO can protect access for a known legacy or regional fleet and supports a mature bidirectional ecosystem in appropriate implementations.
- CCS1 or CCS2 should follow the target region and vehicle population, not be treated as interchangeable.
- SAE J3400/NACS is increasingly important in North America, but vehicle access, adapters and network support remain implementation-specific.
- GB/T and other interfaces may dominate in other markets or imported fleets.
The cabinet power architecture, cable current limits and parking layout determine whether this mix creates capacity or only visual complexity. Freeze the vehicle requirement before freezing the connector count.
Frequently asked questions
Do all Nissan LEAF cars use CHAdeMO?
Do not assume so. Earlier generations in many markets are the best-known native CHAdeMO vehicles, but connector strategy can change by generation and market. Verify the exact car’s inlet and manufacturer documentation.
Can a CCS car use a CHAdeMO charger?
Not natively. The physical connector and communication system differ. Only use a conversion or adapter path explicitly supported for the exact vehicle, adapter and market. Do not treat an online adapter listing as interoperability evidence.
Is CHAdeMO obsolete?
It is declining in some new-vehicle markets but remains relevant to a substantial installed fleet and to particular regions and bidirectional applications. For a site owner, “obsolete” is less useful than local session demand, supportability and transition cost.
Does CHAdeMO support bidirectional charging?
CHAdeMO has long supported V2H/V2G use cases, but a CHAdeMO inlet alone does not prove that a vehicle, charger and local interconnection arrangement support bidirectional operation. Confirm all three, plus the required protection and approval path.
How fast is CHAdeMO?
There is no single CHAdeMO speed. Protocol versions support different envelopes, while the vehicle, charger, cable, temperature and state of charge determine the real session. Specify voltage and current, not only kW.
Can one charger have both CCS and CHAdeMO cables?
Yes, multi-standard configurations exist. Confirm whether the cables can operate simultaneously and how cabinet power is shared. A dual-cable enclosure is not proof of dual full-power output.
Share destination, model years, inlet photos, peak concurrency and available site power.
Final decision rule
For a driver: identify the exact vehicle and inspect its inlet.
For a site owner: count the real vehicles and sessions, decide the required service level, then procure a connector configuration that can demonstrate that duty under test.
If you are planning an international or mixed-fleet DC charging project, send HG Power the destination country, vehicle list with model years, inlet photographs, expected concurrency and available site power. The team can review the connector mix and exact charger configuration before it becomes an expensive site constraint.
Sources and update note
This guide was checked in September 2026 against material from the CHAdeMO Association, US DOE Alternative Fuels Data Center, NREL and manufacturer documentation. Vehicle availability and connector specifications change by market and model year; confirm the exact vehicle before purchase or installation.