QSFP28 and QSFP56 share the same physical cage, the same four-lane electrical architecture and the same I2C management interface — what separates them is modulation. QSFP28 delivers 100 Gb/s as 4 x 25 Gb/s NRZ; QSFP56 delivers 200 Gb/s as 4 x 50 Gb/s PAM4. Pick QSFP28 when your estate is 25G/100G, your servers are on PCIe 3.0, and your fiber plant was built for NRZ optics. Pick QSFP56 when you need 200G per port or a 2 x 100G breakout, your hosts have PCIe 4.0 x16 slots, and your cabling is clean enough to survive PAM4. Every other difference — optics count, cable length ceilings, switch density, total cost — falls out of that single choice, so it is worth ten minutes of attention before you buy either.

What Actually Differs Between QSFP28 and QSFP56

Both form factors expose four transmit and four receive lanes in a 38-pin cage that measures the same in the rack. That physical identity is why the confusion exists: you can slide a QSFP28 module into a QSFP56 port and it will seat perfectly. Electrically the two are not interchangeable in the direction people assume. A QSFP56 port can generally host a QSFP28 module and run it at 100G, because the port's retimer or gearbox can clock down to 25G NRZ per lane. A QSFP28 port cannot make a QSFP56 module run at 200G, because the host silicon has no PAM4 encoder on those lanes and the switch ASIC was never specified for 50G per lane signalling. In practice: upgrades go one way only, from NRZ to PAM4, never back.

The naming follows line rate per lane, not total throughput. The "28" in QSFP28 refers to roughly 28 Gb/s of raw line rate per lane, of which about 25 Gb/s is usable payload after 64b/66b encoding. The "56" in QSFP56 refers to roughly 56 Gb/s of raw line rate per lane, of which about 50 Gb/s is payload. Multiply by four lanes and you get the headline 100G and 200G figures that vendors quote.

Lane Encoding: Why PAM4 Is Not Just "Faster NRZ"

NRZ encodes one bit per symbol by comparing signal voltage against a single threshold. PAM4 encodes two bits per symbol using four distinct voltage levels, which doubles the bit rate at the same symbol rate — and therefore at the same lane count and roughly the same Nyquist frequency. That is the entire commercial argument for QSFP56: double the bandwidth per port without doubling the fiber count, the connector count, or the switch port count.

The price of that trick is margin. Four levels mean one third of the vertical eye height of NRZ, so a PAM4 link tolerates less insertion loss, less crosstalk and less connector contamination before errors appear. PAM4 links also depend on forward error correction at the physical layer (Reed-Solomon FEC, often referred to as KP4 at 50G per lane) to hold a usable bit error rate. Two practical consequences follow. First, both ends of a 200G link must agree on FEC settings; a mismatch is one of the most common reasons a 200G port stays down while the optics look healthy. Second, a fiber plant that ran 100G cleanly for years may need cleaning, re-termination or a patch-panel inspection before it will carry 200G — a cost item that never appears on the bill of materials.

Port Capacity and Density at the Switch Level

The same 1U chassis can look dramatically different depending on which port type it carries. A 32-port QSFP28 switch is a 3.2 Tb/s box; a 32-port QSFP56 switch is a 6.4 Tb/s box in the same rack unit, with the same number of cages, the same cable count and a very similar power draw. That density jump is the main reason 200G platforms displaced 100G platforms in spine roles almost immediately, even where the leaf layer stayed at 100G.

Port count also determines your uplink story. A 64-port QSFP28 leaf gives you 64 x 100G of capacity; a 64-port QSFP56 leaf gives you 64 x 200G. At the same oversubscription ratio, the QSFP56 box can support twice the downstream bandwidth, or half the spine uplinks for the same downstream load — which is where the real savings in optics and switch ports appear.

QSFP28 vs QSFP56 at a Glance

Attribute QSFP28 QSFP56
Lane signalling 25 Gb/s NRZ 50 Gb/s PAM4
Lanes used 4 4
Speed per port 100 Gb/s 200 Gb/s
Physical cage QSFP 38-pin, 4-lane QSFP 38-pin, 4-lane (same)
Management interface I2C EEPROM per SFF-8636 I2C EEPROM per SFF-8636
Typical breakout 4 x 25G 2 x 100G, or 4 x 50G where supported
Passive DAC reach (NVIDIA LinkX family) Up to 5 m Up to 2.5 m
Active copper reach 3 m to 100 m 3 m to 100 m
Multimode fiber reach (SR4) 100 m on OM4 100 m on OM4
Singlemode reach 500 m, 2 km, 10 km, 40 km classes 500 m, 2 km classes
FEC requirement Optional on short NRZ links Effectively mandatory at the PHY
Host interface that feeds it comfortably PCIe 3.0 x16 PCIe 4.0 x16
Representative switch SN2700 (32 x QSFP28, 3.2 Tb/s) SN3700 (32 x QSFP56, 6.4 Tb/s)

Cable Reach: Where the Two Diverges Most

This is the difference that bites procurement teams, because engineers compare per-port speeds and assume the cabling plan carries over unchanged. It does not. In the NVIDIA LinkX cable and transceiver families, 100G QSFP28 passive copper is specified up to 5 m, while 200G QSFP56 passive copper is specified up to 2.5 m. Both use the same 4-lane architecture, but PAM4 burns the signal-integrity headroom that twinax relies on, so the passive copper ceiling drops by half.

If your racks are wired with 3 m passive DACs at 100G — an extremely common in-rack standard — those exact cables will not be qualified for 200G. Active copper and active optical assemblies cover 3 m to 100 m for both generations, and multimode SR4 optics reach 100 m on OM4 at either speed. Singlemode is where the gap widens again: the 100G family spans 500 m, 2 km, 10 km and 40 km reaches, while the mainstream 200G family covers 500 m and 2 km classes. Long-haul campus or cross-building runs therefore stay on 100G optics unless you step to 400G platforms with a different port type entirely.

Breakout: 4 x 25G Versus 2 x 100G

Breakout is often the deciding factor rather than raw speed, because most racks are still full of 25G hosts. A single 100G QSFP28 port breaks out four ways into 4 x 25G, which is why 100G leaves remain the natural home for 25G server fleets. A 200G QSFP56 port breaks out two ways into 2 x 100G — the classic HDR-to-2 x HDR100 splitter cable — or four ways into 4 x 50G where the platform supports it. Notice what is missing: there is no clean 200G-to-25G path. If your rack is 25G-dense, a QSFP56 leaf forces you either to aggregate through a 100G-capable port mode or to keep a QSFP28 layer in place.

That asymmetry explains a pattern visible in most AI and HPC builds: 200G or 400G at the spine for east-west GPU traffic, 100G at the leaf for general compute and storage, and 25G breakout for the long tail of management and legacy hosts. Buying a 200G leaf before the hosts can use it usually converts a bandwidth upgrade into an expensive port-mode exercise.

Switch Platforms: Which Chassis Exposes Which Port

The port type is a property of the chassis, not a preference you can configure. In the Mellanox Spectrum line most commonly found in secondary-market racks, Spectrum-1 platforms such as the SN2700 with 32 QSFP28 ports are 100G-only at 3.2 Tb/s. Spectrum-2 appears in both flavours: the 64-port QSFP28 SN3800 for dense 100G, and the SN3700 with 32 QSFP56 ports for 6.4 Tb/s at 200G per port. Spectrum-3 scales the QSFP56 design up to 64 ports and 12.8 Tb/s in the SN4600, which is the usual pick when a spine has to absorb several hundred 200G leaf uplinks.

Two practical notes when comparing these on a spec sheet. First, the QSFP56 chassis is generally backward compatible at the port level, so a 200G leaf can host 100G optics today and move to 200G later without a hardware swap — that forward path is worth paying for only if you actually intend to use it. Second, check the airflow SKU and the power budget, not just the port count; a 64-port 200G platform draws meaningfully more than a 32-port 100G unit, and connector-side airflow direction must match the aisle layout or the rack will run hot regardless of what the datasheet promises.

Adapter Side: Matching the NIC to the Port Type

Host adapters are where most mismatches actually get discovered, after the switches have shipped. A ConnectX-5 class adapter such as the dual-port 100G MCX516A is a QSFP28 device on PCIe 3.0 x16, which suits a 100G leaf perfectly and is the single most common 100G host pairing in existing estates. A ConnectX-6 class QSFP56 adapter, like the MCX653106A in QSFP56 form, needs PCIe 4.0 x16 to feed 200G without bottlenecking the bus; on a PCIe 3.0 slot it will link, but you will not see the bandwidth you paid for. Older 100G single-port designs such as the MCX4621A remain useful for hosts that only need one high-speed uplink.

Budget the adapter refresh with the switch refresh, or explicitly plan to run the new 200G switch at 100G for a phase. The second option is legitimate and common, but it only pays off if the host fleet refresh is genuinely funded — otherwise you are carrying the power and cost of 200G-capable silicon while moving 100G traffic.

Mixing Modules: Compatibility Rules Worth Knowing

A QSFP56 port hosting a QSFP28 module at 100G is normally fine and is a sensible transition tactic. What is not fine is assuming automatic negotiation. Port speed, FEC mode and, on some platforms, the module's encoded speed rating must be configured explicitly; auto-negotiation between NRZ and PAM4 does not exist as a universal fallback. Verify three things before mixing: that the port is configurable to 100G, that the FEC setting on the port matches the module and the far end, and that the switch firmware release you are running supports the specific optic part number. Vendor compatibility matrices list part numbers, not just speeds, and the difference matters at 200G far more than it did at 100G.

Keep a written module inventory per rack. In mixed estates, the fastest way to lose an afternoon is a 200G link that comes up at 100G because one end was populated from the wrong spares bin.

Cost: Where the Money Actually Goes

Comparing sticker prices per port is the least useful way to compare these two generations, because the cost is distributed across five line items that move in opposite directions. Per port, a 200G QSFP56 port costs more than a 100G QSFP28 port. Per gigabit of switching capacity, it is usually cheaper, because you get twice the bandwidth from the same chassis, the same rack unit and the same port count. Optics follow the same pattern: a 200G module costs more than a 100G module, but you buy half as many for the same aggregate bandwidth. Cabling is roughly neutral per link and slightly cheaper per gigabit at 200G, since one 200G DAC replaces two 100G DACs in a two-rail design. The items that reliably go up are the host side — PCIe 4.0 servers and QSFP56 adapters — and the fiber remediation you may need before PAM4 will run clean.

There is also a sparing cost that rarely gets modelled. Every distinct optic type in the estate needs spares, and a mixed 100G/200G estate carries two inventories instead of one. Projects that skip this line item tend to discover it during the first failure, at the worst possible moment, when the only spare on the shelf is the wrong generation.

When 200G Is Worth It, and When It Is Not

Move to QSFP56 when at least two of these are true: the workload is east-west and bandwidth-bound (distributed training, storage replication, NVMe-oF, MPI across nodes); the host fleet already has PCIe 4.0 x16 slots free; the fiber runs are inside the row and under 100 m; and the switch is a spine or an AI-leaf where port count is the binding constraint. Stay on QSFP28 when the rack is 25G-dense and depends on 4 x 25G breakout, when the hosts are PCIe 3.0, when you have long singlemode runs beyond 2 km, or when the traffic profile is north-south and nowhere near saturating 100G.

For most estates the correct answer is not one or the other but a deliberate two-tier design: 100G QSFP28 where the hosts live, 200G QSFP56 where the fabric aggregates. That split keeps the breakout flexibility where it is needed and takes the density benefit where it actually pays.

Frequently Asked Questions

Can I plug a QSFP28 module into a QSFP56 port?

Physically yes — the cage and connector are identical. Electrically it depends on the platform: most QSFP56 ports can be configured to 100G and will host a QSFP28 module, but the port speed and FEC mode usually have to be set explicitly rather than negotiated. Confirm the combination in the switch vendor's compatibility matrix for your firmware release before standardising on it.

Is QSFP56 backward compatible with my existing 100G DAC cables?

Not for 200G operation. Passive copper for 200G QSFP56 is specified to about 2.5 m in the NVIDIA LinkX family, while 100G QSFP28 passive copper reaches 5 m — so a 3 m 100G DAC that has worked for years is outside the qualified passive range at 200G. Those cables remain usable if the port is run at 100G, which is why many teams keep a 100G phase in the migration.

Why does a 200G link need FEC when my 100G links do not?

Because 50G per lane PAM4 signalling has a much smaller margin than 25G NRZ. Forward error correction at the physical layer compensates for the reduced eye height introduced by four-level signalling, so it is effectively part of the standard rather than an option. Both ends must agree on the FEC mode; a mismatch is a common cause of a port that shows light but never comes up.

Does 200G double my fiber count?

No. QSFP56 uses the same four lanes, in the same duplex pairs, as QSFP28 — the bandwidth doubling comes from modulation, not from additional strands. What changes is the quality requirement: PAM4 is less tolerant of insertion loss, contamination and poor terminations, so an existing multimode plant may need cleaning or re-termination before it will carry 200G reliably.

Should I buy a 200G switch if my servers are still on 100G?

Only if you have a funded host refresh inside your planning horizon. A QSFP56 chassis will happily run 100G today and gives you a forward path without a hardware swap, but you pay for higher power draw and a second optics generation in the meantime. If the host fleet is staying on PCIe 3.0 for the next two years, a dense 100G platform usually delivers more usable bandwidth per unit of spend.

If you are sizing a 100G-to-200G step and want a second opinion before committing, the useful starting point is a ports list, a host inventory with PCIe generations, and your longest cable run. Browse switch platforms, 100G and 200G adapters, and server hardware availability on zhongxindata.hk, or send that list on WhatsApp to +86 13068616914 and we will map it against current stock and flag the compatibility traps before you order optics.

Published by Zhongxin Data | November 2026