Logic Levels: VIL, VIH, VOL, VOH and Noise Margins
Understand VIL, VIH, VOL, VOH and noise margins so you can read datasheets correctly and avoid intermittent logic failures in your designs.

Contents & prerequisites
Why Logic Levels Matter in Digital Design
The bridge between analog voltages and digital interpretation
Every digital signal is, underneath the abstraction, an analog voltage. A microcontroller pin, a logic gate input, a serial bus line — all of them are physically continuous voltages that a receiving circuit must classify into one of two buckets: logic 0 or logic 1. That classification is not free. It requires a threshold, and real circuits need two thresholds, not one, because a single trip point would be hopelessly sensitive to noise. The specifications that define those thresholds — VIL, VIH, VOL, and VOH — are the actual contract between chips on a board. Everything built on top of Boolean logic, from AND and NAND gates upward, depends on these four numbers being respected.
How noise affects digital signal integrity
A wire carrying a "clean" 3.3 V logic high is never actually sitting at exactly 3.3 V. Ground bounce, crosstalk from a neighboring trace, inductive ringing from a fast edge, IR drop across a long power plane — all of these add noise on top of the intended level. If the digital interpretation threshold were a single point, a few millivolts of noise near that point could flip the perceived logic value every few nanoseconds, causing glitches that STA tools and simulators would never predict from the ideal logic diagram alone. Logic-level specifications exist precisely to build a cushion against this.
Why datasheets specify these parameters
Manufacturers characterize VIL, VIH, VOL, and VOH under specific test conditions — supply voltage, temperature, and output current — and guarantee them as worst-case limits, not typical values. A datasheet entry for VOH is not "what the output usually does"; it's "the worst voltage you will see under the stated load, anywhere in the specified temperature and supply range." Designing against anything looser than the guaranteed worst case is how field failures happen: the bench prototype works because the one sample tested had better-than-spec margins, and the production units at the temperature extreme do not.
Input Logic Levels: VIL and VIH
VIL (Voltage Input Low): Maximum voltage recognized as logic 0
VIL is the highest voltage that a receiving input is guaranteed to still interpret as a logic 0. Any voltage at or below VIL is safely read as low. For example, a classic 74HC-family CMOS input on a 5 V rail might specify VIL(max) around 1.0 V — consult the specific part's datasheet for the guaranteed figure, since it varies by family and supply voltage.
VIH (Voltage Input High): Minimum voltage recognized as logic 1
VIH is the lowest voltage guaranteed to be read as a logic 1. Anything at or above VIH is safely high. Continuing the same example, that 74HC input might guarantee VIH(min) around 3.5 V on a 5 V supply.
The undefined region between VIL and VIH
Between VIL and VIH lies a gap the datasheet makes no promises about. A voltage sitting in that band might be read as 0 by one instance of the chip, as 1 by another, or — worse — oscillate between interpretations on a single device as it drifts with temperature or supply noise. Internally, this is the linear region of the input transistor's transfer characteristic, the same kind of transition region you'd see plotted on a diode's forward-bias I-V curve near the knee voltage: not a hard switch, but a continuous region where behavior is ill-defined and sensitive to exact operating conditions. A signal that dwells in this zone — a slow-rising clock edge, a bus line with a weak driver, a long unterminated trace — can cause a receiving gate's output to oscillate or even draw excess supply current as both halves of a CMOS inverter conduct simultaneously. This is why rise/fall time specifications and Schmitt-trigger inputs exist: to minimize the time a signal spends in the undefined band.
How temperature and supply voltage affect input thresholds
VIL and VIH are not fixed numbers; datasheets typically give them as a function of supply voltage (VCC), and separately guarantee them across a temperature range (commercial 0–70°C, industrial −40–85°C, or automotive grades). As VCC drops, CMOS thresholds generally scale down with it since they derive from the transistor switching point as a fraction of supply. Temperature shifts transistor threshold voltages and carrier mobility, nudging the trip point in ways that differ between process technologies. Always use the datasheet table for the actual operating voltage and temperature corner of your design, not the typical room-temperature number.
Output Logic Levels: VOL and VOH
VOL (Voltage Output Low): Maximum voltage a gate outputs for logic 0
VOL is the highest voltage a gate's output will produce when driving a logic 0, under a specified output current (IOL) and supply condition. A typical CMOS output might guarantee VOL under 0.33 V at a modest load current — again, check the specific device.
VOH (Voltage Output High): Minimum voltage a gate outputs for logic 1
VOH is the lowest voltage guaranteed when driving a logic 1, at a specified sourcing current (IOH). For many CMOS outputs this sits close to VCC minus a few hundred millivolts under light load.
Load dependency of output levels
VOL and VOH are not constants — they are specified at a particular test current, and they degrade as load current increases. An output pin behaves somewhat like a Thevenin source with finite output resistance: as the sinking or sourcing current rises, the actual VOL rises and the actual VOH falls, the same loaded-source behavior described generally by the voltage divider relationship between source resistance and load. Pulling more current than the datasheet's test condition means you cannot assume the published VOL/VOH numbers still hold.
Fanout and its effect on output voltage
Fanout is the number of downstream inputs a single output can drive while still meeting its VOL/VOH guarantees. Each input load draws a small input leakage or input current; summed across many parallel loads, that current can push VOL up past its spec or pull VOH down past its spec even though each individual input current is tiny. Exceeding rated fanout is a common, hard-to-spot source of marginal logic levels, particularly on older TTL designs with resistive input loads and on buses with many receivers.
Noise Margins: The Safety Boundary
Low-level noise margin: VOL to VIL gap
The low noise margin, NML = VIL(max) − VOL(max), is the amount of noise that can be added to a logic-0 output before the receiving gate might misread it as high.
High-level noise margin: VOH to VIH gap
The high noise margin, NMH = VOH(min) − VIH(min), is the equivalent cushion on the high side.
Why symmetric margins matter for reliability
A design with a generous NMH but a razor-thin NML is only as reliable as its weakest margin. Real noise sources — ground bounce, crosstalk, supply droop — don't respect which side of the swing they attack, so robust designs aim for margins that are reasonably balanced on both ends, not just a large average.
Calculating noise margins from datasheet values
Worked example, using illustrative values you should replace with your actual part's datasheet numbers:
VOH(min) = 2.4 V VOL(max) = 0.4 V
VIH(min) = 2.0 V VIL(max) = 0.8 V
NMH = VOH(min) - VIH(min) = 2.4 - 2.0 = 0.4 V
NML = VIL(max) - VOL(max) = 0.8 - 0.4 = 0.4 V
Here both margins are 0.4 V — the circuit tolerates up to 400 mV of noise riding on either rail before a logic error becomes possible. If a system has 150 mV of expected ground bounce plus 100 mV of crosstalk coupling, that 0.4 V margin is getting thin and deserves closer scrutiny under worst-case temperature and supply corners.
Logic Family Variations: TTL vs. CMOS
Different thresholds across technology families
Classic TTL defines its input thresholds around VIL(max) ≈ 0.8 V and VIH(min) ≈ 2.0 V regardless of supply, because the thresholds are set by bipolar junction voltage drops rather than a fraction of VCC. CMOS families instead typically scale thresholds as a percentage of VCC (often around 30%/70% of the rail for standard CMOS, tighter for some newer low-voltage families). This difference is why TTL-to-CMOS and CMOS-to-TTL interfacing was such a persistent headache in mixed designs: a TTL output's VOH might not clear a CMOS input's VIH by much, especially at reduced supply voltages, yielding thin NMH even though NML looks fine.
Interfacing chips with mismatched logic levels
When mixing logic families or voltage domains — 1.8 V, 2.5 V, 3.3 V, 5 V — check VOH of the driver against VIH of the receiver, and VOL of the driver against VIL of the receiver, explicitly. A 3.3 V CMOS output driving a 5 V TTL input is usually fine because TTL's VIH is low; the reverse, a 5 V output into a 3.3 V-only input, can exceed absolute maximum ratings and cause damage via the input's protection diodes, the same clamping structures described by reverse-bias breakdown behavior in protection diodes. Level shifters or open-drain with proper pull-ups are the standard fixes.
Pull-up and pull-down effects on actual voltages
Open-drain and open-collector outputs rely entirely on an external pull-up resistor to establish VOH; that pull-up forms a simple divider with the line's leakage currents and the driving transistor's off-state resistance. Choosing too weak a pull-up slows rise time and risks not reaching VIH within the bit period; too strong a pull-up increases power and may violate IOL ratings when the line is driven low.
Practical Design Considerations
Reading logic levels from IC datasheets
Locate the DC electrical characteristics table, find VIL, VIH, VOL, VOH, and note the exact test conditions column — supply voltage, output current, and temperature. Numbers quoted without matching test conditions are not comparable between parts.
Testing actual logic levels with a multimeter or oscilloscope
A multimeter can confirm static VOH/VOL on a quiescent output, but it cannot catch transient undershoot, overshoot, or ringing. An oscilloscope with adequate bandwidth, probed directly at the receiving pin (not just at the driver), is necessary to see whether an edge actually clears VIH/VIL cleanly and how much time it spends in the undefined band.
Margin erosion from cascaded gates and transmission lines
Each gate stage in a chain adds its own worst-case degradation; if every stage in a long chain is simulated only at typical conditions, the design can look fine while the true worst-case cascade — slowest driver into least sensitive receiver, repeated across many stages — eats the entire margin. Long traces acting as transmission lines add reflection-induced ringing that can temporarily push a signal below VOL or above VOH targets at the receiver, independent of the driver's DC specification.
Worst-case analysis under temperature and supply variation
Always evaluate NML and NMH at the corner that minimizes them: typically minimum VCC and the temperature extreme where VOH is weakest and VIH is highest (or the mirror case for the low side). A margin that looks comfortable at 25°C and nominal VCC can vanish at −40°C and minimum supply.
Troubleshooting Intermittent Logic Failures
Symptoms of inadequate noise margin
Classic symptoms include failures that appear only at temperature extremes, only on certain board revisions, only when a specific neighboring signal toggles, or that vanish when a scope probe (with its added capacitance) is attached — a strong hint that the signal was marginal to begin with.
How to verify marginal signals in the lab
Probe directly at the receiving pin under worst-case supply and thermal conditions, measure actual rise/fall time through the VIL–VIH window, and compare the settled high and low levels against the datasheet's guaranteed VOH/VIH and VOL/VIL, not typical values.
Common culprits: weak drivers, long traces, and crosstalk
Underdriven buses (too much fanout or too weak a pull-up), excessively long unterminated traces causing ringing, and capacitive or inductive crosstalk from adjacent fast-switching lines are the three most common root causes of noise-margin violations in practice. Each is solvable at the board level — buffering, termination, spacing, or guard traces — once the margin analysis has identified where the budget is actually being spent.
Learning
Sign in to track your progress.
Evidence
Public projects engineers linked to Logic Levels: VIL, VIH, VOL, VOH and Noise Margins.
No engineer has linked a project to this topic yet. Built something that proves it? Add the project and tag it with digital-electronics-logic-levels-vil-vih-vol-voh-and-noise-margins — it then shows here and on your public profile.
