←Back to Technical Sheets
In-Depth Technical Sheet

DVB Standards & C/N Reference
Every MODCOD, Its Threshold, and What the Numbers Actually Mean

The complete DVB-S2 and DVB-S2X performance tables, transcribed from the standards themselves — 28 S2 modes, 45 S2X modes, down to −9.9 dB for very-low-SNR operation. Plus the part most tables omit: these are ideal figures from simulation with perfect synchronisation and no phase noise, and the difference between them and what your receiver needs is the whole subject of a link budget.

  • MODCOD tables
  • C/N vs Es/N0 vs Eb/N0
  • Symbol rate & bandwidth
  • Standards family
  • Margin

1. Scope and sources

Every figure on this page was read from the published standard, not from a secondary table. The two documents that matter are ETSI EN 302 307-1 V1.4.1 (2014-11) for DVB-S2 and ETSI EN 302 307-2 V1.4.1 (2024-08) for DVB-S2X. Both were downloaded from the ETSI portal and parsed directly; the version numbers were confirmed against the ETSI directory rather than assumed.

What this page deliberately does not contain: DVB-T2 C/N figures. Reasonable to expect them here, and they are genuinely useful — but they are not in EN 302 755, the DVB-T2 standard. That document specifies the system without stating required C/N per mode; the performance figures live in the DVB-T2 implementation guidelines, which could not be retrieved while preparing this sheet. Rather than reproduce numbers from a secondary source and present them with the same authority as the satellite tables, section 9 says where they live and stops there. The DVB-T2 structural parameters below are from EN 302 755.

Terrestrial and cable C/N thresholds also depend far more on channel model than satellite ones do. A satellite link is close to AWGN; a terrestrial one is a multipath channel where the required C/N for the same modulation and code rate can differ by several decibels between a fixed-roof and a portable-indoor reception model. A single number per mode is meaningful for satellite in a way it is not for terrestrial.

2. Es/N0, Eb/N0 and C/N — the distinction that costs money

These three are used interchangeably in conversation and are not interchangeable in arithmetic. Confusing them is the most common way a link budget comes out wrong by two or three decibels, which at Ku band is the difference between two antenna sizes.

RatioNormalised perWhere it appears
Es/N0Transmitted symbolWhat the DVB-S2 and S2X tables give. Independent of code rate, because the code rate is already reflected in which row you are reading
Eb/N0Information bitStandard in communications theory. Lets you compare schemes of different spectral efficiency on equal footing
C/NA stated bandwidthWhat a receiver reports and what a link budget produces. Meaningless without knowing the bandwidth

The conversion between the first two is given in the note under Table 13 itself:

Eb/N0 = Es/N0 − 10·log₁₀(ηtot)

where ηtot is the spectral efficiency in bits per symbol. The sign matters and catches people out. For a high-efficiency mode η > 1, so Eb/N0 is lower than Es/N0. For a strong low-rate code η < 1 and Eb/N0 is higher. Worked from the table's own numbers:

Modeη (bit/symbol)Es/N0 (dB)10·log₁₀(η)Eb/N0 (dB)
QPSK 1/40,490243−2,35−3,10+0,75
QPSK 3/41,4874734,031,722,31
8PSK 2/31,9806366,622,973,65
16APSK 3/42,96672810,214,725,49
32APSK 5/64,11954014,286,158,13

QPSK 1/4 is the instructive row: a negative Es/N0 of −2,35 dB and a positive Eb/N0 of +0,75 dB describe the same link. The carrier really can sit below the noise floor and still be decoded, because each information bit is spread across more than two symbols. Anyone who says "you cannot receive a signal below the noise floor" is thinking in Eb/N0 while reading an Es/N0 number.

For C/N, the relationship to Es/N0 depends on the bandwidth you measure in. Measured in a bandwidth equal to the symbol rate, C/N and Es/N0 are numerically the same. Measured in the occupied bandwidth — symbol rate times one plus roll-off — C/N is lower by 10·log₁₀(1 + α):

Roll-off α10·log₁₀(1 + α)Meaning
0,351,30 dBDVB-S2 default, inherited from DVB-S
0,250,97 dBDVB-S2 option
0,200,79 dBDVB-S2 option
0,150,61 dBDVB-S2X addition
0,100,41 dBDVB-S2X addition
0,050,21 dBDVB-S2X addition
So "C/N = 7 dB" is not a complete statement. In symbol-rate bandwidth it means Es/N0 = 7 dB, comfortably above 8PSK 2/3. In occupied bandwidth at α = 0,35 the same measurement means Es/N0 = 8,3 dB. Whenever a datasheet or a receiver quotes C/N, establish the reference bandwidth before comparing it with any table on this page.

3. What "works" means — the QEF definition

Every threshold on this page is the point at which the system reaches Quasi-Error-Free operation. That phrase has a precise definition in EN 302 307-1, and it is not "no errors":

QEF for DVB-S2: "less than one uncorrected error-event per transmission hour at the level of a 5 Mbit/s single TV service decoder", corresponding approximately to a transport stream Packet Error Ratio below 10⁻⁷ before the demultiplexer.

Two consequences that matter operationally. First, the target is tied to a 5 Mbit/s service — a higher-bitrate service passes more packets per hour, so the same PER produces more error events. Second, QEF is a threshold with a cliff below it: LDPC coding means performance does not degrade gracefully. A link half a decibel above threshold is perfect; half a decibel below it fails almost completely. There is very little of the gradual picture degradation that analogue and even DVB-S exhibited.

DVB-S2X changed the metric. The S2X tables are specified at FER = 10⁻⁵ — Frame Error Ratio, the proportion of FECFRAMEs received in error — not the PER = 10⁻⁷ used for S2. These are different quantities measured on different objects, so S2 and S2X threshold figures are not strictly comparable at the third decimal place. For engineering purposes they are close enough to tabulate together, which is what section 5 does, but a specification document comparing them should say which metric it means.

4. Why these are "ideal" figures, and what to add

This is the caveat that most reproductions of these tables drop, and it is the difference between a table and a link budget. EN 302 307-1 states the conditions under which its numbers were obtained:

Condition assumedReality
Figures from computer simulationNot measured on hardware
50 LDPC fixed-point decoding iterationsA receiver that stops earlier to save power performs worse
Perfect carrier and synchronisation recoveryReal demodulators lose a fraction of a decibel acquiring and tracking
No phase noiseEvery real LNB and receiver contributes phase noise, and higher-order APSK is far more sensitive to it
AWGN channelReal links add rain fade, interference, and transponder non-linearity
Normal FECFRAME (64 800 bits), no pilotsShort FECFRAMEs cost 0,2 to 0,3 dB more, per the standard

The standard is explicit about the conclusion: "For calculating link budgets, specific satellite channel impairments should be taken into account." In other words the table gives you a floor, and the implementation margin plus channel impairments plus rain fade allowance sit on top of it. Treating an ideal Es/N0 as a design threshold produces a link that works in clear sky and fails on the first weather event.

How close is this to theory, and how close is it usually claimed to be? EN 302 307-1's introduction says DVB-S2 allows QEF operation "at about 0,7 dB to 1 dB from the Shannon limit". That figure is the gap from the constellation-constrained capacity — the best achievable with that specific constellation. Measured against unconstrained Gaussian capacity, the gap is larger: computing 10·log₁₀(2η − 1) from the table's own spectral efficiencies gives 1,07 dB for QPSK 1/2, 1,93 dB for 8PSK 2/3, 2,14 dB for 32APSK 5/6 and 2,85 dB for 32APSK 9/10. Both statements are correct about different quantities. Neither is a reason to expect a real receiver to hit the table.

5. DVB-S2 — the complete Table 13

All 28 modes, transcribed from EN 302 307-1 V1.4.1 Table 13. Es/N0 at QEF, PER = 10⁻⁷, AWGN, FECFRAME length 64 800, no pilots. Decimal commas are as printed in the standard.

ModeSpectral efficiency (bit/symbol)Ideal Es/N0 (dB)
QPSK 1/40,490243−2,35
QPSK 1/30,656448−1,24
QPSK 2/50,789412−0,30
QPSK 1/20,9888581,00
QPSK 3/51,1883042,23
QPSK 2/31,3222533,10
QPSK 3/41,4874734,03
QPSK 4/51,5871964,68
QPSK 5/61,6546635,18
QPSK 8/91,7664516,20
QPSK 9/101,7886126,42
8PSK 3/51,7799915,50
8PSK 2/31,9806366,62
8PSK 3/42,2281247,91
8PSK 5/62,4785629,35
8PSK 8/92,64601210,69
8PSK 9/102,67920710,98
16APSK 2/32,6372018,97
16APSK 3/42,96672810,21
16APSK 4/53,16562311,03
16APSK 5/63,30018411,61
16APSK 8/93,52314312,89
16APSK 9/103,56734213,13
32APSK 3/43,70329512,73
32APSK 4/53,95157113,64
32APSK 5/64,11954014,28
32APSK 8/94,39785415,69
32APSK 9/104,45302716,05
Read the overlaps — they are where the engineering decisions live. 8PSK 3/5 needs 5,50 dB for 1,780 bit/symbol, while QPSK 9/10 needs 6,42 dB for almost exactly the same 1,789 bit/symbol. The 8PSK mode delivers the same throughput at nearly a decibel less C/N. Similarly 16APSK 2/3 (8,97 dB, 2,637 bit/symbol) beats 8PSK 8/9 (10,69 dB, 2,646 bit/symbol) by 1,7 dB at equal efficiency. A higher-order constellation with a stronger code frequently outperforms a lower-order one straining at 9/10 — so "lower modulation order is more robust" is only true at equal code rate, which is rarely the comparison anyone actually faces.

6. DVB-S2X — the extended modes

From EN 302 307-2 V1.4.1 Table 20a. Es/N0 at QEF, FER = 10⁻⁵, normal FECFRAMEs, 50 iterations. The second figure is the informative non-linear hard-limiter channel result — the same mode through a saturated transponder, at optimised input back-off and 10 % roll-off.

MODCODη (bit/symbol)Es/N0 linear AWGN (dB)Csat/(N0·Rs) non-linear (dB)
QPSK 2/90,434841−2,85−2,45
QPSK 13/450,567805−2,03−1,60
QPSK 9/200,8891350,220,69
QPSK 11/201,0885811,451,97
8APSK 5/9-L1,6472114,735,95
8APSK 26/45-L1,7136015,136,35
8PSK 23/361,8961736,126,96
8PSK 25/362,0621487,027,93
8PSK 13/182,1451367,498,42
16APSK 1/2-L1,9722535,978,4
16APSK 8/15-L2,1048506,559,0
16APSK 5/9-L2,1932476,849,35
16APSK 26/452,2816457,519,17
16APSK 3/52,3700437,809,38
16APSK 3/5-L2,3700437,419,94
16APSK 28/452,4584418,109,76
16APSK 23/362,5247398,3810,04
16APSK 2/3-L2,6352368,4311,06
16APSK 25/362,7457349,2711,04
16APSK 13/182,8562319,7111,52
16APSK 7/93,07722510,6512,50
16APSK 77/903,38661811,9914,00
32APSK 2/3-L3,29195411,1013,81
32APSK 32/453,51019211,7514,50
32APSK 11/153,62053612,1714,91
32APSK 7/93,84122613,0515,84
64APSK 32/45-L4,20642813,9817,7
64APSK 11/154,33865914,8117,97
64APSK 7/94,60312215,4719,10
64APSK 4/54,73535415,8719,54
64APSK 5/64,93663916,5520,44
128APSK 3/45,16324817,7321,43
128APSK 7/95,35555618,5322,21
256APSK 29/45-L5,06569016,9821,6
256APSK 2/3-L5,24151417,2421,89
256APSK 31/45-L5,41733818,1022,9
256APSK 32/455,59316218,5922,91
256APSK 11/15-L5,76898718,8423,80
256APSK 3/45,90085519,5724,02

Three things to read out of this table:

7. Very Low SNR modes

S2X adds modes for links that DVB-S2 simply cannot close, using π/2 BPSK and very low code rates. From Tables 20b and 20c of EN 302 307-2 V1.4.1, at FER = 10⁻⁵:

MODCODFECFRAME lengthIdeal Es/N0 (dB)
π/2 BPSK-S 1/515 390−9,9
π/2 BPSK-S 11/4515 390−8,3
π/2 BPSK 1/530 780 (medium)−6,85
π/2 BPSK 1/514 976−6,1
π/2 BPSK 11/4530 780 (medium)−5,50
π/2 BPSK 4/1514 976−4,9
π/2 BPSK 1/330 780 (medium)−4,00
π/2 BPSK 1/316 200−3,72

The medium and short XFECFRAME tables use 75 decoding iterations rather than 50 for the BPSK modes — more decoder work traded for threshold. At −9,9 dB the carrier is nearly ten decibels below the noise, which is what makes very small terminals, deep rain fade operation and emergency links feasible at all.

Why the frame length appears in this table and not the S2 one. S2X defines several FECFRAME lengths — normal 64 800, medium 30 780, short 16 200, and the odd lengths 15 390 and 14 976 for specific BPSK modes — and the threshold depends on which is used, because a longer code performs closer to capacity. When someone quotes a VL-SNR figure, the frame length is part of the specification, not an implementation detail.

8. From symbol rate to bitrate and bandwidth

Two relationships turn a MODCOD into the numbers you actually need. Both come straight from the table's own definitions.

Useful bitrate = Rs × η      (η from the spectral efficiency column)
Occupied bandwidth = Rs × (1 + α)  (α = roll-off factor)

Worked examples, computed from the table values above:

MODCODRs (Msym/s)αOccupied BW (MHz)Useful bitrate (Mb/s)Ideal Es/N0 (dB)
8PSK 2/335,30,2042,3669,926,62
8PSK 2/330,00,2036,0059,426,62
QPSK 3/427,50,3537,1240,914,03
16APSK 3/430,00,1534,5089,0010,21
32APSK 5/633,00,1036,30135,9414,28
QPSK 1/45,00,356,752,45−2,35

The first row is a real transponder configuration referenced elsewhere on this site — 35 300 ksym/s, FEC 2/3, DVB-S2 8PSK — which works out to roughly 70 Mb/s of usable transport stream in about 42 MHz, needing at least 6,62 dB before any margin. The last row is the same arithmetic at the other extreme: a narrow 5 Msym/s carrier delivering 2,45 Mb/s but closing at −2,35 dB.

Two caveats on the spectral efficiency column. First, the values are computed for no pilots; enabling pilot symbols for easier carrier recovery reduces useful throughput. Second, they are normalised to a bandwidth equal to the symbol rate. To express efficiency per unit of occupied bandwidth, EN 302 307-2 says explicitly to divide by (1 + roll-off) — so 32APSK 5/6 at α = 0,10 gives 4,1195 / 1,10 = 3,745 bit/s/Hz of occupied spectrum, not 4,12.

The bitrate figure is the transport stream rate, which is what you compare against the numbers tsbitrate reports. If a measured stream rate does not match the arithmetic above, either the symbol rate, the code rate, or the pilot setting is not what you were told.

9. The standards family

Every version below was confirmed against the ETSI portal while preparing this sheet. Where a standard is old, that is because it is stable, not because it is superseded — DVB-S from 1997 still carries services today.

SystemStandardVersion confirmedNotes
DVB-SETSI EN 300 421V1.1.2 (1997-08)QPSK only, convolutional plus Reed-Solomon coding, roll-off fixed at 0,35
DVB-S2ETSI EN 302 307-1V1.4.1 (2014-11)LDPC plus BCH, QPSK to 32APSK, roll-off 0,35/0,25/0,20. Source of section 5
DVB-S2XETSI EN 302 307-2V1.4.1 (2024-08)Adds 8APSK, 64/128/256APSK, π/2 BPSK VL-SNR, finer code rates, roll-off down to 0,05, beam hopping. Sections 6 and 7
DVB-TETSI EN 300 744V1.6.2 (2015-10)OFDM, QPSK to 64-QAM, 2K and 8K FFT
DVB-T2ETSI EN 302 755V1.4.1 (2015-07)Structural parameters in the next table. Contains no required-C/N table
DVB-CETSI EN 300 429V1.1.2 (1997-08)Single-carrier QAM, 16 to 256-QAM, Reed-Solomon
DVB-C2ETSI EN 302 769—OFDM with LDPC, up to 4096-QAM. Little deployed
T2-MIETSI TS 102 773V1.4.1 (2016-03)Modulator interface. See the MPEG-TS sheet
Video and audio codecsETSI TS 101 154V2.10.1Which codecs may ride in the container
Service informationETSI EN 300 468V1.19.1 (2025-02)See the PSI/SI sheet
Measurement guidelinesETSI TR 101 290V1.4.1See the DVB errors sheet
Conditional accessETSI TS 103 197V1.5.1 (2008-10)See the CA sheet
Adaptive streamingETSI TS 103 285—DVB-DASH. Uses ISOBMFF and CMAF, not transport stream

9.1 DVB-T2 structural parameters

From EN 302 755 V1.4.1. These are specified values, unlike the C/N thresholds:

ParameterValues
FFT sizes1K, 2K, 4K, 8K, 16K, 32K
Guard intervals1/128, 19/256, 19/128 (with the larger FFTs) and 1/32, 1/16, 1/8, 1/4
ConstellationsQPSK, 16-QAM, 64-QAM, 256-QAM
Constellation rotationAvailable, but not used with 256-QAM in the T2-Lite profile
Multiple servicesPhysical Layer Pipes (PLPs), each independently modulated and coded
Transmit diversityMISO using a modified Alamouti scheme, with pilot modification
Where DVB-T2 C/N figures live. Not in EN 302 755. The required C/N per mode is published in the DVB-T2 implementation guidelines, and unlike the satellite case a single figure per mode is not very meaningful: the same modulation and code rate can differ by several decibels depending on whether the channel model is fixed rooftop, portable outdoor or portable indoor. Ask which channel model any quoted DVB-T2 C/N figure assumes; if the answer is not available, the figure is not comparable to anything.

10. Margin — what to add to a table figure

The tables give an ideal threshold. A design threshold is that plus everything the simulation excluded. The components are well known even though their magnitudes are installation-specific, and the honest position is to measure them rather than assume a rule of thumb.

ComponentWhy it applies
Implementation marginReal demodulator versus ideal simulation: imperfect carrier recovery, finite decoder iterations, quantisation. Comes from the receiver's datasheet, not from a standard
Phase noiseLNB and receiver oscillators. Roughly negligible for QPSK, significant for 32APSK and above
Short FECFRAME penalty0,2 to 0,3 dB — this one is quantified, by EN 302 307-1 itself
Pilot overheadPilots ease carrier recovery but reduce useful throughput; the table's efficiencies assume none
Transponder non-linearityQuantified for S2X in the hard-limiter column of section 6 — up to 4,45 dB for 256APSK 3/4
Adjacent channel and co-channel interferenceRaises the effective noise floor. The standard's threshold is against C/N+I, not C/N alone
Rain fade allowanceFrequency, geography and availability target dependent. The largest term at Ka band and often the dominant one at Ku
Antenna pointing and polarisation errorInstallation quality. Small, but it does not improve over time
Why a generous margin is not simply "safer". Margin is bought with bandwidth. Choosing a mode 3 dB more robust than necessary means accepting materially lower spectral efficiency for the same transponder — 8PSK 2/3 rather than 16APSK 3/4 costs roughly a third of the capacity. The engineering question is not "how much margin can I add" but "what availability do I need, and what is the cheapest mode that delivers it". That is a decision about the service, not about the modulation.

For a service where continuity matters more than efficiency, there is a structural alternative to buying margin in decibels: receive the same transponder at more than one site and fail over between them. That trades RF margin for geographic diversity, which addresses rain fade — a local phenomenon — in a way that no amount of coding gain at a single site can. The TSDuck cookbook covers the mechanics with tsswitch, and the tuner sheet covers how the sources differ.

11. Standards and sources

SpecificationRole here
ETSI EN 302 307-1 V1.4.1 (2014-11)DVB-S2. Downloaded and parsed. Source of Table 13 in section 5, the QEF definition in section 3, the ideal-conditions caveats in section 4, the Eb/N0 relation in section 2, and the roll-off options
ETSI EN 302 307-2 V1.4.1 (2024-08)DVB-S2X. Downloaded and parsed. Source of Table 20a in section 6, Tables 20b and 20c in section 7, the additional roll-off factors, and the bandwidth-normalisation note in section 8
ETSI EN 302 755 V1.4.1 (2015-07)DVB-T2. Downloaded; source of the structural parameters in 9.1, and the basis for stating that it contains no required-C/N table
ETSI EN 300 421, EN 300 429, EN 300 744DVB-S, DVB-C, DVB-T. Versions confirmed against the ETSI portal for the family table
ETSI TR 102 376DVB-S2 implementation guidelines, referenced by EN 302 307-1 for the LDPC decoding assumptions

12. About the author

Gleb Sazanov

Project Leader

Gleb Sazanov is an accomplished Chief Technology Officer (CTO) with over 20 years of experience in software development, system architecture, and cloud-based solutions. As the CTO of SATLINE, a leading provider of virtual and colocation services tailored to SATCOM businesses, Gleb drives the company’s technological strategy, fostering innovation and efficiency in data center services. His expertise spans various domains, including DevOps, system scaling, and high-performance infrastructure management. With a deep passion for cutting-edge technologies, Gleb plays a pivotal role in shaping the future of the SATCOM industry.