How to Power Servo Motors with Raspberry Pi Safely

The Raspberry Pi is a fantastic brain for robotics projects, but it is a terrible power source for motors. This is the single most important lesson every maker learns — usually the hard way, after watching their Pi reboot randomly or, worse, release the magic smoke. Micro servo motors like the SG90, MG90S, and their metal-gear cousins are everywhere in Raspberry Pi projects: pan-tilt camera mounts, robot arms, walking robots, and animatronics. They are cheap, tiny, and surprisingly power-hungry. Powering them safely from a Raspberry Pi requires understanding why the naive approach fails and what to do instead.

Why the Naive Approach Fails

The Raspberry Pi's GPIO Pins Are Not Power Supplies

The 5V pins on the Raspberry Pi's 40-pin header are connected directly to the board's input power rail. On a Raspberry Pi 4 or 5, that rail can supply a couple of amps in theory — but only if your power supply can deliver it, and only if you are not asking the rail to do anything else. The Pi itself, its USB peripherals, and its SD card all draw from the same source. A single SG90 micro servo can pull 200–650 mA during movement and stall currents approaching 1 A. Two or three servos moving at once can easily exceed what your official 5V/3A power supply can spare, and the resulting voltage sag will reset the Pi mid-operation.

The Brownout Problem

Micro servos are inductive loads with brushed DC motors inside. When a servo starts moving, it draws a current spike. When it stalls — which happens constantly in pan-tilt mounts when the servo hits its mechanical limit — it draws its maximum stall current continuously. This causes the 5V rail to sag. The Pi's undervoltage detector trips, and the board either throttles or reboots. Even if the Pi survives, the servo gets less voltage, produces less torque, and behaves erratically. This is the classic "my servo jitters and my Pi reboots" symptom that fills forum threads.

Signal Voltage Is a Separate Issue

The control signal is a different story from power. Servo signal lines expect a PWM pulse between roughly 1 ms and 2 ms, repeated at 50 Hz. A 3.3V logic-level PWM signal from the Raspberry Pi's GPIO pin is usually accepted by hobby servos, which nominally expect 5V logic but have tolerant input thresholds. Most SG90 and MG90S units work fine with 3.3V signals. However, some larger or higher-quality servos are stricter, and long signal wires pick up noise. Keep signal wires short, and if a servo misbehaves, a level shifter is the fix — never connect a 5V signal directly back into a Pi GPIO, which is not 5V tolerant.

The Safe Power Architecture

Separate the Power Rails

The golden rule: the servo power rail and the Raspberry Pi power rail must be separate, sharing only a common ground. Power your Pi from its own official supply. Power your servos from a dedicated 5V source — a battery pack, a bench supply, or a separate wall adapter — sized for the stall current of all servos combined, not their idle current.

Size the Supply Correctly

Do the math before you buy anything. For micro servos:

• Idle current: ~10 mA per servo
• Moving current: ~200–400 mA per servo
• Stall current: ~650 mA to 1 A per servo (check your datasheet)

If you are running four SG90s in a pan-tilt array, plan for at least 4 × 0.7 A ≈ 2.8 A of headroom on the servo rail, plus margin. A 5V/5A supply is a sensible choice. Undersizing the supply is the second most common mistake after tying the servo rail to the Pi's 5V pin.

Share a Common Ground

The servo supply's ground and the Pi's ground must be connected together. Without a common reference, the PWM signal has no meaning and the servo will twitch or ignore commands entirely. This is the one wire that must cross between the two power domains.

Add Bulk Capacitance

Even a well-sized supply has transient response limits. Solder a large electrolytic capacitor — 470 µF to 1000 µF, rated 10V or higher — across the servo power rail near the servos. This capacitor acts as a local reservoir for current spikes, smoothing the rail and preventing the voltage dips that cause brownouts. Some makers add a 0.1 µF ceramic capacitor in parallel for high-frequency noise. This single addition fixes a surprising number of "mysterious reboot" problems.

Practical Wiring for Micro Servos

The Three-Wire Servo Connector

Every hobby servo has three wires: power (usually red), ground (brown or black), and signal (orange, yellow, or white). Verify colors with your datasheet — they are not universal.

A Safe Wiring Diagram in Words

1. Servo red wires → dedicated 5V servo supply positive terminal.
2. Servo brown/black wires → dedicated supply ground and Pi ground (common ground).
3. Servo signal wires → Pi GPIO pins (any GPIO capable of PWM; GPIO 12, 13, 18, and 19 are the hardware PWM pins on most models).
4. Pi power input → its own official power supply, untouched by servo current.
5. Bulk capacitor across the servo supply terminals, close to the servos.

Use a Power Distribution Board or Breadboard Power Rail

For more than one or two servos, do not daisy-chain power through breadboard rails — they have resistance and current limits. Use a screw-terminal distribution block, a servo power breakout board, or solder a proper bus. Keep power wires short and thick relative to signal wires.

Driving the Signal Safely from Software

Use Hardware PWM When Possible

The Raspberry Pi has hardware PWM on a few GPIO pins. Libraries like pigpio and gpiozero can generate stable 50 Hz PWM in software, but software-timed PWM jitters under load, which makes servos buzz and jitter. For smooth motion, prefer hardware PWM pins or a dedicated servo driver board.

Consider a PCA9685 Servo Driver

The PCA9685 16-channel PWM driver is the standard solution for multi-servo projects. It runs on its own 5V logic supply (which can come from the Pi's 3.3V or 5V rail — it draws almost nothing), drives up to 16 servos, and has its own power input terminals for the servo rail. This cleanly separates signal generation from servo power and offloads PWM timing from the Pi's CPU. It is the single best upgrade for any project with more than two servos.

Set Safe Pulse Widths in Code

Never command a servo beyond its mechanical range. Standard micro servos accept 500–2400 µs pulses, but many are only safe from 1000–2000 µs. Driving a servo into its mechanical stop causes continuous stall current, heat, and gear stripping. Calibrate your endpoints in software and clamp them.

Protecting the Pi Itself

Add a Flyback Diode or Use a Driver Board

Brushed motors generate voltage spikes when they switch off. A servo's internal electronics usually handle this, but cheap clones sometimes do not. If you are paranoid — and after losing a Pi, you will be — use a servo driver board with built-in protection, or add a diode across the servo power rail. More importantly, never back-feed the Pi's 5V pin from an external supply while the Pi is also powered by USB. That is a recipe for a dead Pi.

Fuse the Servo Rail

A resettable PTC fuse or a small inline fuse on the servo supply protects against a shorted servo or wiring mistake. It costs pennies and can save your project.

Watch for Heat

Micro servos are not designed for continuous duty. If a servo is warm to the touch after a minute of operation, it is stalling or overloaded. Fix the mechanics — reduce load, add gearing, or use a stronger servo — rather than feeding it more current.

A Checklist Before You Power Up

• [ ] Servo rail is a separate supply from the Pi's power input.
• [ ] Servo supply is rated for total stall current plus margin.
• [ ] Common ground connects servo supply and Pi.
• [ ] Bulk capacitor (470–1000 µF) is across the servo rail.
• [ ] Signal wires are short and connected only to GPIO inputs.
• [ ] PWM pulse widths are clamped to the servo's safe range.
• [ ] Servo rail is fused.
• [ ] Nothing back-feeds the Pi's 5V pin.

Follow this architecture and your micro servo projects will run smoothly for years. Skip it, and you will join the long, sad tradition of makers who learned about inductive loads by watching their Pi reboot in the middle of a demo. The servos are cheap. The Pi is not. Power them like you know the difference.