74HC595 Guide: Pinout, Cascading and Startup Control

74HC595 shift-register guide showing serial loading, a separate latch and coordinated eight-output control

74HC595 Guide: Pinout, Cascading and Startup Control

The 74HC595 expands a serial connection into eight parallel outputs while a separate storage register keeps the displayed pattern steady. Successful designs depend on three decisions: matching the controller's logic levels, separating shifting from latching, and keeping the load inactive until a known output frame has been loaded.

1. Which 74HC595 pins need special attention?

The table uses TI names for the common 16-pin arrangement. Nexperia uses DS, SHCP, STCP, MR, Q0-Q7 and Q7S for the corresponding functions. Translate names by function before comparing schematics; a different drawing convention does not necessarily indicate different behavior.

74HC595 standard 16-pin top-view pinout with serial data, shift clock, latch clock, active-low clear and output enable identified
Figure 1. Original Chip-seek top-view pin map, based on TI SN74HC595 section 5 and Nexperia 74HC/HCT595 section 6. Pin 1 is at the upper left. Physical package dimensions and land patterns require the exact package drawing.
Pin TI / Nexperia name Function and connection check
14 SER / DS Serial data input; stable around the rising shift-clock edge.
11 SRCLK / SHCP Rising-edge shift clock; normally connected to the controller's serial clock.
12 RCLK / STCP Rising-edge storage clock; controlled separately for a complete-frame update.
13 OE Active-low parallel-output enable; high means high impedance.
10 SRCLR / MR Active-low asynchronous shift-register clear; high during normal shifting.
9 QH' / Q7S Serial chain output; connect to the next device's serial input.
15, 1-7 QA-QH / Q0-Q7 Eight latched parallel outputs, in that order.
16 / 8 VCC / GND Supply and ground; place local bypass capacitance close to these pins.

Use the notch or pin-one mark to establish orientation. A top-view drawing read as a bottom view reverses the connections. Also distinguish a 16-pin SOIC from a TSSOP or a leadless package: matching pin count does not establish footprint compatibility.

The pin map and register behavior are documented in the TI SN74HC595 datasheet, sections 5 and 8. For naming and package cross-checks, use the Nexperia 74HC595/74HCT595 datasheet.

2. Why are shifting and latching separate?

The input shift register assembles the next eight-bit word. The storage register holds the word already presented at the parallel outputs. A rising SRCLK edge moves serial data through the first register; a rising RCLK edge copies its contents into the second.

74HC595 functional diagram separating the serial shift register, output storage register and output-enable stage
Figure 2. Original functional illustration based on the manufacturers' logic diagrams. Clear acts on the shift register; OE acts on the parallel output stage. The serial cascade output bypasses the storage register.

That separation lets a controller prepare the next display or control pattern while the previous pattern remains visible. Keep RCLK quiet throughout the transfer, then issue one latch pulse after the final shift edge and the required timing interval. The outputs update after the latch-to-output propagation delay.

Tying both clocks together removes this complete-frame behavior. The storage register receives the previous shift-register state at each common edge, so it trails shifting by one clock. This can be intentional, but it is unsuitable when intermediate patterns must remain hidden.

Conceptual 74HC595 timing sequence showing eight rising shift-clock edges followed by a separate latch pulse and a parallel-output frame change
Figure 3. Original conceptual timing diagram for the byte 0xA5, MSB first. Horizontal spacing illustrates event order, not measured nanoseconds. Observe the selected device's setup, hold, pulse-width and propagation specifications.

For a concrete reference, TI's SN74HC595 timing table specifies a 25 ns minimum SER setup time and a 19 ns minimum separation from SRCLK rising to RCLK rising at VCC = 4.5 V over its specified operating temperature range. The minimum clock high and low durations are each 20 ns under those conditions. These entries belong to that device and condition; do not apply them unchanged to 2 V operation or another manufacturer's part.

A hardware SPI peripheral can generate data and shift-clock signals. Configure its sampling relationship so data is stable before each rising SRCLK edge; a conventional mode-0 transfer is one starting configuration. Generate RCLK independently, and wait for physical transfer completion before latching. A DMA submission or a transmit-buffer-empty flag may precede the final clock at the pins.

3. Can a 3.3 V MCU drive a 5 V 74HC595?

The answer depends on guaranteed output and input limits. A controller pin described as 3.3 V does not necessarily guarantee a 3.3 V high under every load and temperature. Compare its minimum VOH with the receiver's minimum VIH, and its maximum VOL with the receiver's maximum VIL.

Reference device Supply condition Input limits Selection implication
TI SN74HC595 2-6 V recommended supply; threshold example at 4.5 V VIH minimum 3.15 V; VIL maximum 1.35 V at 4.5 V A nominal 3.3 V source requires an actual guaranteed-level comparison; margin can be insufficient.
TI SN74HCT595 4.5-5.5 V recommended supply VIH minimum 2.0 V; VIL maximum 0.8 V TTL-level inputs can suit a 3.3 V controller whose output limits meet these requirements.

The HCT limits come from the TI SN74HCT595 datasheet, section 6.3. HCT is a candidate for the controller-to-register interface, not a claim that every mixed-voltage connection becomes compatible. Its output voltage still follows its own supply and load conditions.

Apply this check to all control inputs, including latch, clear and output enable. An OE pull-up to 5 V also requires checking the connected MCU pin's voltage tolerance. A suitably rated open-drain control stage or level translator may be needed. Likewise, a 5 V serial output returning to a 3.3 V MCU needs its own compatibility check.

Powering HC at the controller's rail can simplify logic matching when the load permits it. Check output drive and timing at that lower supply, and evaluate what happens when either rail is absent. Do not assume an unpowered device tolerates an actively driven input.

4. How do two devices receive the correct bytes?

Connect U1 QH' to U2 SER, share SRCLK and RCLK, and provide a common reference ground. U1 is the register nearest the MCU. Bits travel through U1 into U2 while both devices shift on the same clock edges; storage outputs remain on the previously latched frame.

Two cascaded 74HC595 registers with QH prime connected to SER, shared shift and latch clocks, and far-device byte transmitted before near-device byte
Figure 4. Original two-device chain illustration. With MSB-first transmission, send the far-device byte before the near-device byte. Shared power, ground, clear, OE and local bypass components are omitted from the signal-flow drawing.

Suppose U2 must hold 0xA5 and U1 must hold 0x3C. Send 0xA5 first, then 0x3C, with eight MSB-first clocks per byte. After 16 clocks, U1 contains 0x3C and U2 contains 0xA5. One RCLK pulse transfers both words to the output registers. In this convention QA corresponds to bit 0 and QH to bit 7 of each final byte.

For a chain of N devices, a full refresh requires 8N shift clocks. The ideal transfer time is 8N divided by the shift-clock frequency. Eight devices at an illustrative 1 MHz therefore take 64 microseconds to shift; software, latch timing, blanking and settling add overhead. This calculation describes a protocol budget, not a guaranteed operating speed.

Maximum usable frequency also depends on serial-output propagation, receiving-device setup time, clock skew and board loading. Review hold time as well as setup time. Slowing the clock increases setup margin but does not automatically repair a same-edge hold-time problem caused by skew. Long clock branches and cables deserve signal-integrity checks rather than progressively larger firmware delays.

Record byte order and output numbering in the schematic or firmware interface. A pattern that appears reversed can result from sending the nearest device first, reversing bit order, or physically labeling the outputs in the opposite direction. Use a walking-one pattern before testing an application image.

5. How can startup flashes be prevented?

A register without a specified power-on state should not be treated as an automatic all-off device. Firmware also starts after a period in which MCU pins may be inputs or perform boot functions. Establish output blanking in hardware, then release it only after the supply and control signals are valid.

74HC595 initialization sequence with hardware output blanking, defined clocks and clear, a loaded inactive frame, a latch pulse and final output enabling
Figure 5. Original initialization sequence derived from the datasheet function table. The inactive frame depends on load polarity. Hardware blanking and load-side bias must also cover reset and power-sequencing conditions.
  1. Hold OE high. Use a suitable pull-up or supervisory arrangement so outputs remain disabled while the MCU starts. Size it for leakage, noise and the control stage's drive capability.
  2. Establish defined controls. Hold SRCLK and RCLK at inactive levels. If using SRCLR, assert it low while respecting its pulse-width requirement.
  3. Release clear and load a full frame. Return SRCLR high, meet its recovery requirement, and shift the application-specific inactive pattern through every device.
  4. Latch the known frame. After the final shift edge and required setup interval, pulse RCLK. Allow the stored outputs to settle.
  5. Enable the load. Drive OE low only when the stored frame and surrounding circuitry are ready.

Zero is not universally off. An LED wired from the positive rail to an output can illuminate when that output sinks current. An active-low driver input may also turn on at zero. Define the inactive pattern from the actual load wiring, and provide load-side bias where high impedance would otherwise leave a control node floating.

Clearing the shift register alone does not change an already latched pattern. To transfer cleared zeros to the outputs, a storage-clock event is still required. The sequence above loads the complete desired frame explicitly, so it also handles applications whose inactive pattern is not zero.

Test MCU reset, watchdog recovery and brownout separately from cold startup. OE held high controls the outputs only within the device's valid operating conditions; it is not a guarantee for every supply ramp. Loads that must remain inactive throughout power transitions may need an independent driver inhibit or supervisor.

6. How much current can the outputs deliver?

The 74HC595 is a logic-output register. Its absolute maximum current is a stress limit, not a recommended LED-current setting. TI lists 35 mA per output and 70 mA through VCC or GND as absolute maxima for SN74HC595, while guaranteed output-voltage limits are characterized at smaller currents.

Budget every active channel, package dissipation and supply return together. Eight channels each assigned 10 mA already imply 80 mA in the relevant common current path before other contributions. That simple sum is a reason to reject the assumption, not a suggested operating point.

For direct LED drive, fit individual current-limiting resistors and calculate the worst case using supply tolerance, LED forward-voltage spread and the output's loaded voltage. Recheck simultaneous-channel patterns. A resistor chosen from a nominal 5 V supply and an unloaded output estimate can produce the wrong current.

For relays, solenoids or higher-current indicators, evaluate a separate transistor stage or an appropriate power-output shift register. These options change output behavior, protection and thermal design. TI's TPIC6B595 power shift register, for example, uses low-side open-drain outputs and a different 20-pin arrangement; it is not a drop-in 16-pin HC replacement.

TI recommends a local 0.1 microfarad bypass capacitor for a single-supply logic device in its SN74HC595 supply guidance. Keep the capacitor close to VCC and ground, and provide a short return path. A capacitor at the MCU end of a long cable does not replace decoupling at each remote register.

7. Which alternatives need a design change?

Candidate Why consider it? Required validation
Another manufacturer's 74HC595 Second-source evaluation within the same logic family. Exact package and land pattern, temperature grade, loaded output levels, timing, input transitions and reset behavior.
74HCT595 TTL-compatible input thresholds at its specified supply. Supply range, complete interface levels, package, timing and power sequencing.
74HC164 Serial-to-parallel expansion where intermediate output states are acceptable. Different 14-pin arrangement and no separate storage register; firmware and hardware redesign.
TPIC6B595 A power-output architecture for suitable sinking loads. Different package, low-side output polarity, load supply, clamp behavior, current and thermal limits.

The SN74HC164 datasheet shows why a similar serial function is insufficient to establish interchangeability. Its outputs follow the shift-register stages without the HC595's separate storage-clock interface. Match the system behavior before comparing price or availability.

Start a second-source search with the complete manufacturer part number and package suffix. The Chip-seek 74HC595 catalog search is a candidate-discovery route; an approved substitute still requires engineering review. A matching search term is not a compatibility certificate.

8. What should be checked when a chain fails?

Observed symptom Checks to make first Useful verification
Pattern changes while data is loading Latch clock tied to shift clock, extra RCLK edges, or wrong GPIO assignment. Capture SRCLK and RCLK together through one complete frame.
Second device repeats or loses bits QH used instead of QH', wrong byte order, incomplete transfer or serial timing margin. Send different walking-one patterns to the near and far devices.
LEDs flash during boot OE default, unknown stored data, boot-pin activity and load polarity. Observe OE, RCLK, supply ramp and a representative output through reset.
Works at one voltage but fails at another Input thresholds, loaded drive voltage, supply range and speed assumptions. Compare guaranteed levels; measure at the receiver's pin and reference ground.
Only long chains fail Clock fanout, return path, skew, local decoupling and edge quality. Inspect near and far clock edges and the serial input at the failing stage.

Begin with a slow, single-device test and a known load, then add devices while keeping the pattern repeatable. A symptom suggests a test; it does not prove a root cause. TI's Implications of Slow or Floating CMOS Inputs explains why undefined or slow control inputs deserve attention even when the serial data looks correct.

9. Frequently asked questions

Does pulling SRCLR low turn every output off?

No. It clears the shift register, while the output storage register retains its previous data until RCLK transfers a new word. Even a latched all-zero word is not an all-off command for every load polarity.

Can OE be used to blank a display?

Yes, OE high disables the parallel output stage without erasing either register. Check enable and disable timing and the load's high-impedance behavior. OE does not blank the serial cascade output.

Which byte should be sent first in a two-chip chain?

With the MSB-first convention described here, send the far device's byte first and the near device's byte second. Transfer all 16 bits before the common latch edge.

Can a 74HCT595 replace a 74HC595?

It is a candidate only after checking the operating supply, input thresholds, package, output loading and timing. HCT's TTL-compatible inputs do not imply operation across the HC device's entire supply range.

Can a relay connect directly to a 74HC595 output?

Do not assume so. Evaluate a suitable driver stage or power-output register against coil current, voltage, inductive transients and startup behavior. Logic-current ratings alone are insufficient for selecting a coil driver.

How many devices can be cascaded?

There is no universal board-independent count. The useful limit follows from refresh time, shared-clock loading, skew, serial timing, power distribution and the physical interconnect. Validate the intended chain on its actual PCB and wiring.

10. What belongs in the sourcing checklist?

A useful RFQ makes the approved requirements explicit rather than asking only for a generic 595. Include the following information so a proposed alternate can be reviewed against the same design constraints.

  • Full original MPN, manufacturer, package code, temperature grade and quantity.
  • Register supply range, controller levels, interface direction and power sequence.
  • Channel current, load type, simultaneous-output pattern and required inactive state.
  • Chain length, shift frequency, latch behavior and physical interconnect.
  • Approved datasheet revision, traceability requirements and alternate-approval process.

Request a comparison against these fields before approving a substitute. Availability, date codes, packaging and delivery commitments need confirmation for the actual quotation. For the purchasing workflow, see the Chip-seek electronic component availability guide.

Conclusion

A reliable 74HC595 design keeps serial shifting, output latching and output enabling distinct. Verify voltage levels and load current, document the byte order, and initialize a complete inactive frame before releasing hardware blanking. Evaluate replacements against those same requirements, including the exact package and operating conditions.

Source the right shift register for your BOM

Search 74HC595 part numbers or submit a BOM / RFQ with your full MPN, package, quantity and interface requirements. Mark proposed alternates as subject to engineering approval.

Technical sources

Source documents checked on October 29, 2026. Illustrations are original explanatory drawings; no bench measurements are claimed.

Check stock by part number

Turn this insight into a sourcing decision.

Need pricing or a drop-in alternative? Submit a BOM / RFQ or talk to our team.