Can an SFP28 Port Use SFP+ Optics? What to Verify Before Ordering
Check whether an SFP28 port can run 10G SFP+ optics by verifying host support, port mode, software, FEC, coding and both link endpoints.

An SFP+ module inserted into an SFP28 port can usually work at 10G — if that exact SFP28 port, host and software support 10G mode. In the other direction, an SFP28 module inserted into an SFP+ port cannot deliver 25G; only a dual-rate SFP28 module that supports 10G may work at 10G, and only if the host supports it.
Physical fit is not proof of a link. The module must be recognised, the port must support the requested rate, and both ends must agree on speed, FEC and optical interface. The safe answer is therefore sometimes — not automatically. Treat the shared form factor as the start of the review, not the approval. Confirm each point in the host datasheet or transceiver support matrix, or with the supplier, before ordering.
Compatibility at a Glance
Use this table as a starting point only. Every “Sometimes” cell depends on the exact host model, port, line card and software — confirm it in the host datasheet, transceiver support matrix or supplier confirmation before ordering.
| Port | SFP module (1G) | SFP+ module (10G) | SFP28 module (25G) | Dual-rate SFP28 (25G/10G) |
|---|---|---|---|---|
| SFP port (1G) | Yes — 1G | No — the port cannot run 10G | No — the port cannot run 25G | No — its lowest rate is 10G, above the port’s 1G limit |
| SFP+ port (10G) | Sometimes — 1G if the host supports 1G mode | Yes — 10G | No 25G — a 25G-only module cannot deliver 25G in a 10G port | Sometimes — 10G if the module and host support 10G mode |
| SFP28 port (25G) | Sometimes — 1G if the host supports 1G mode | Sometimes — 10G if the host supports 10G mode | Yes — 25G | Yes — 25G, or 10G if the module and host support 10G mode |
This guide is for network engineers, system integrators and technical buyers deciding whether existing 10G SFP+ optics can be reused during a 25G-capable platform rollout.
Why the Same Shape Is Not the Same Electrical Interface
SFP, SFP+ and SFP28 share the SFF-8432 mechanical form factor, so the modules fit the same cage. The electrical interface is different: SFP+ is built around a 10G SerDes lane, while SFP28 is built around a 25G SerDes lane. A host port must therefore support the lower rate explicitly; the shared cage does not make the rates interchangeable.
Three separate questions have to be answered.
| Layer | What to check |
|---|---|
| Physical fit | The module fits the cage and connector. This proves nothing about the link rate. |
| Port capability | The port, line card and software support the requested rate on that exact port. |
| Link compatibility | Both ends agree on speed, FEC, wavelength, fiber type and module identity. |
Keep these three layers separate. A module can be physically compatible and electrically impossible on that port, or electrically possible and still fail because the remote end is not configured the same way.
The Two Directions: SFP+ in an SFP28 Port, and SFP28 in an SFP+ Port
SFP+ module in an SFP28 port
This is the usual reuse case. It can work at 10G when the SFP28 port, line card and software support 10G mode on that exact port, the module is recognised and coded for the host, and the remote end is configured for 10G with matching FEC and optics. If the port is locked to 25G only, or 10G support was added only in a later software release, the link will not come up at 10G.
SFP28 module in an SFP+ port
This direction cannot deliver 25G, because the SFP+ port cannot run faster than 10G. A 25G-only SFP28 module will not link at 25G in that port, and may not link at all. Only a dual-rate SFP28 module that supports 10G may work, at 10G, and only if the host supports that mode — see the next section.
Dual-Rate SFP28 Modules
A dual-rate SFP28 module lists more than one supported rate in its datasheet — for example 25G and 10G. Do not assume a module labelled 25G is dual-rate: check the exact part number and its supported rates, and confirm that the host supports the lower rate on the selected port. If either side lists only 25G, the SFP+ port cannot use it at 10G.
When a dual-rate module is used in an SFP+ port, set the port to 10G explicitly where the host requires it, and configure the remote end the same way.
FEC and Matching the Rate at Both Ends
Do not expect the link to come up at the lower rate on its own. SFP+ and SFP28 use different link rates, so both ends must be set to the same speed, with matching forward error correction (FEC) and negotiation behaviour for that mode.
The defensible sequence is:
- Set or confirm the supported speed at both endpoints.
- Verify that the chosen media is supported in that mode.
- Apply the host's documented negotiation and FEC settings.
- Confirm that any port-group or breakout change is intentional.
- Save the original configuration for rollback.
Do not copy a working configuration from a different host, port or software version and assume it applies here.
Coding and the Vendor Compatibility List
Use the exact part number, not only the module type. Confirm the module's exact model and version, its vendor coding profile, and whether that profile is accepted by the host for the selected port and software version.
- Vendor coding profile for the host
- Exact module model and version
- Supported speeds and rates in the module datasheet
- Optical interface, wavelength and reach — confirm the exact limits in the datasheet or with the supplier
- Power and insertion behaviour for that host
Start with the exact hardware and software combination. Useful evidence includes:
- A hardware table listing supported port speeds.
- A transceiver matrix naming the port, software train and optic family.
- A configuration guide showing the required speed or breakout command.
- Release notes describing when support was added, changed or restricted.
- A controlled test on the same hardware and software build.
Do not generalize from a different host model, port or software train. A third-party seller's generic statement is not evidence for an exact host model.
Fiber and Wavelength Must Match at Both Ends
The remote optic must match the local optic: the same wavelength, the same fiber type, the same connector, and a reach that covers the route, with loss within the limits in the module datasheet — confirm the exact limits with the supplier where the datasheet does not state them.
If the link uses a bidirectional (BiDi) module, the two ends need complementary transmit and receive wavelengths on a single fiber. A matched BiDi pair is required; two identical BiDi modules will not link. For planning, see the 25G BiDi upgrade planning guide.
Check the fiber path as well: fiber type, connector, polarity, passive components and loss. The optical transceiver upgrade checklist can be used to gather these details before ordering.
Host Limits: Port Groups, Line Cards and Software
Do not request a compatibility answer from “SFP28 port” alone. Port-group, line-card and software limits are common reasons a 10G mode is unavailable on one port and available on another.
Collect the following before asking for a compatibility check:
- Host vendor and complete device model
- Line card, NIC or daughter card when applicable
- Exact port number and port group
- Network operating system and software or firmware version
- Current port speed, configured speed and available speed choices
- Breakout or channelization mode, if the port belongs to a shared group
- Existing optic part number and coding profile
- Remote host, port and optic identity
- Fiber type, connector, route length and passive components
- Required digital optical monitoring (DOM/DDM) visibility
- Link acceptance criteria and rollback plan
Port-group details matter because some ports share a SerDes or a breakout mode: changing the mode can change the rates available on neighbouring ports. Confirm the port-group mode in the host documentation before changing it.
For a structured pre-order review, see the SFP28 vs SFP+ compatibility check guide.
Use a Controlled Validation Before a Wider Rollout
Where documentation is incomplete, test a sample on the same hardware and software build before ordering in quantity. A sample that works in a different chassis, line card or software version is not evidence for the target port.
Record:
- Module recognition and reported identity
- Configured and operational port speed
- Link state at both ends
- DOM/DDM availability, when supported
- Receive power compared with the exact module limits
- FEC state and relevant error counters
- Traffic test duration and acceptance criteria
- Reboot, reseat or failover behavior when required by the change plan
DOM/DDM is useful operating evidence, not proof of compatibility on its own. For what DOM/DDM can and cannot prove, see the guide on whether DOM/DDM proves transceiver compatibility.
Common Reasons the 10G Link Still Fails
When the 10G link still fails, work through the most common causes before replacing components:
- The port accepts the module mechanically but does not support 10G on that port.
- The correct speed is supported only after a particular software release.
- The line card supports 10G on some ports but not the selected port.
- The local side is set to 10G while the remote side remains at 25G.
- The module is recognized but its coding profile is not accepted for that host.
- The optics use the wrong wavelength, fiber type or BiDi direction.
- FEC or negotiation settings do not match the documented 10G behaviour.
- The fiber path has excessive loss, dirty connectors or incorrect polarity.
Replace components only after the cause is identified; replacing a working module will not fix a port-mode or configuration mismatch.
Pre-Order Checklist
Use a short decision record before ordering. If any row depends on an assumption, record it as an open item and confirm it before the order is placed.
| Item | Record before ordering |
|---|---|
| Host | Exact device, line card, port, port group and software version, with the supported rate for that port. |
| Module | Exact part number, supported rates and coding profile, confirmed for that host. |
| Link | Fiber type, wavelength, connector, distance and loss budget for both ends. |
| Settings | Speed, FEC and auto-negotiation settings, agreed at both ends. |
| Evidence | Datasheet, transceiver matrix or controlled test record for the exact combination. |
Five Gates Before Ordering
Do not place the order until every gate below can be answered from evidence, not from an assumption.
- Host gate — the exact device, line card, port, port group and software support the requested rate, confirmed in the host datasheet or transceiver matrix.
- Module gate — the exact module identity, its supported rates and its coding profile are confirmed for that host.
- Link gate — both endpoints, fiber type, wavelength, connector and reach match, and any BiDi pair is complementary.
- Configuration gate — speed, auto-negotiation and FEC are set the same way at both ends, and any port-group or breakout change is intentional.
- Validation gate — the documentation review is recorded, a controlled sample is tested where evidence is incomplete, and a rollback plan is ready.
FAQ
Use these questions to confirm the decision before ordering.
Can I use a 10G SFP+ module in a 25G SFP28 port?
Sometimes. The port, line card and software must support 10G on that exact port, the module must be recognised, and the remote end must be configured for 10G. Do not assume it will work.
Can I use an SFP28 module in an SFP+ port to get 25G?
No. An SFP+ port cannot run at 25G. A 25G-only SFP28 module will not deliver 25G in that port.
Will a dual-rate SFP28 module work in an SFP+ port?
Only if the exact module and the host both support 10G mode on that port. Check the module datasheet for its supported rates and confirm the host support before ordering.
Does an SFP+ module in an SFP28 port require reconfiguration?
Use the host vendor's documentation to check whether the port must be set to 10G explicitly. Do not assume the port will fall back to 10G on its own.
Does coding a module for a vendor ensure compatibility?
No. Coding is one layer. Port capability, supported rate, FEC, optical interface and software support must also match.
What exact details should I send before ordering?
Send both host models, line card and port details, software version, module part number, fiber type, distance and quantity, so the combination can be checked against the host's documented compatibility.
Prepare the Port Evidence Before Ordering
If you need to reuse 10G SFP+ optics in an SFP28 port, send the exact platform, distance and quantity so the correct option can be checked against the host's documented compatibility.


