A reactor, in drive terms, is simply an inductor, a coil, wired in series with a drive to add impedance where you need it. Where you put it decides what it does. A line reactor sits between the power supply and the drive's input and smooths the current the drive draws, cutting harmonics, softening voltage transients, and stopping nuisance trips. A load reactor sits between the drive's output and the motor and softens the fast switching edges that stress the motor and its cable. Same component, two jobs, and knowing which side a problem lives on is half of choosing the right one. They are cheap, passive, and often the first thing an engineer reaches for when a drive misbehaves on either its input or its output.
Line / Load Reactor in one line: A line reactor is an inductor placed on the input (line) side of a variable frequency drive to add impedance that reduces input harmonics, buffers voltage spikes and sags, and prevents nuisance overvoltage tripping. A load reactor is the same type of component placed on the output (load) side between the drive and motor, where it slows the fast switching edges to protect motor insulation and reduce cable-related stress. The difference is entirely which side of the drive the choke sits on and, therefore, which problem it solves.
A reactor is an inductor, and an inductor resists sudden changes in current. Wire one in series with a drive and it adds series impedance that smooths current flow and blunts fast transients. That single property, opposition to abrupt current change, is behind everything a reactor does, whether on the input or the output. The reactor's value is often expressed as a percentage impedance, which describes how much it impedes current relative to the drive's rating; a larger percentage means more smoothing but also more voltage dropped across the reactor, so sizing is a balance.
Position matters because the problems on the two sides of a drive are different. On the input side, the drive's rectifier draws current in sharp bursts, creating harmonics that flow back into the supply, and the input is also where incoming voltage spikes and sags from the grid arrive. On the output side, the drive's inverter produces fast-switched voltage pulses that travel down the motor cable and stress the motor. A reactor helps with both, but it is helping with unrelated problems depending on where it sits, so you choose and size it for the specific trouble on that side.
This is also what distinguishes a reactor from a harmonic filter and from a dedicated dV/dt filter. A line reactor provides modest, broad, inexpensive harmonic reduction and transient protection, whereas a purpose-built harmonic filter tackles harmonics more aggressively and at higher cost. A load reactor provides general output smoothing, while a dedicated dV/dt or sine-wave filter targets the switching edges more precisely for severe long-cable cases. Reactors are the simple, general-purpose, first-line tool; the specialized filters are what you reach for when a reactor is not enough.
On the input side, a line reactor addresses several related problems at once. Its most cited benefit is reducing the harmonic current the drive draws, because the added impedance forces the rectifier to pull current more smoothly instead of in sharp peaks, which lowers the distortion the drive injects back into the supply. It also buffers the drive against the grid: incoming voltage transients and spikes are absorbed by the reactor before they reach the drive's sensitive front end, and momentary sags and swells are cushioned, all of which protects the drive and reduces faults.
A very practical reason line reactors get installed is to stop nuisance tripping. Drives on stiff supplies, close to a large transformer, or where capacitor switching elsewhere on the system injects transients, can suffer repeated overvoltage or overcurrent trips that have nothing to do with the load. Adding series impedance with a line reactor cushions those events and the trips stop. Because a line reactor is inexpensive and easy to add, it is a common first remedy when a drive keeps faulting for no obvious load-side reason.
There is a trade-off, which is the voltage the reactor drops. Because it adds impedance in series, some voltage is lost across the reactor under load, slightly reducing the voltage available to the drive. A modestly sized line reactor makes this negligible, but oversizing to chase more harmonic reduction can starve the drive of voltage, so the reactor is sized to get worthwhile benefit without robbing too much voltage. This is why line reactors provide meaningful but limited harmonic improvement; pushing harmonic performance further means moving to a dedicated filter or a low-harmonic drive rather than simply enlarging the reactor.
On the output side, a load reactor sits between the drive and the motor, and its job is to soften the fast voltage edges the inverter produces. By slowing how quickly the voltage rises on each switching pulse, it reduces the voltage overshoot that fast edges cause at the motor terminals on longer cable runs, easing the stress on motor winding insulation. It also smooths the output current somewhat, which can reduce motor heating and audible noise. On installations with long motor leads, a load reactor is a common, economical measure to protect the motor short of a full dV/dt or sine-wave filter.
Diagnosing which reactor a situation calls for comes down to reading the symptoms. Trouble that shows up as supply-side harmonics, drive nuisance trips, or sensitivity to grid disturbances points to the input and a line reactor. Trouble that shows up as motor insulation failures, overheating motors, or problems that worsen with cable length points to the output and a load reactor. It is entirely possible for a single drive to warrant both, a line reactor for a dirty or troublesome supply and a load reactor for a long cable run to the motor, since they solve independent problems on independent sides.
For operators managing drives across many sites, the value of remote monitoring is spotting which side is misbehaving without a truck roll. Recurring overvoltage or overcurrent faults visible in a cloud SCADA fault log, especially ones tied to grid events rather than load changes, suggest an input-side problem a line reactor could cure. A pattern of premature motor failures on long-lead wells points to an output-side problem a load reactor could ease. Seeing these patterns remotely lets an engineer specify the right, inexpensive choke for the right side before dispatching anyone, rather than diagnosing each troubled drive by hand at the wellsite.
They are the same type of component, an inductor or choke, placed on different sides of the drive. A line reactor goes on the input (line) side to reduce input harmonics, buffer voltage transients, and prevent nuisance tripping. A load reactor goes on the output (load) side between the drive and motor to soften the fast switching edges that stress motor insulation and cable, especially on long runs. The position determines which problem the reactor solves.
Often, yes, when the tripping is caused by the supply rather than the load. Drives on stiff supplies or exposed to voltage transients from nearby capacitor switching can trip repeatedly for reasons unrelated to the motor. A line reactor adds series impedance that cushions those transients, which frequently stops the trips. Because it is inexpensive and easy to add, a line reactor is a common first remedy when a drive keeps faulting with no obvious load-side cause.
No, though they overlap. A line reactor provides modest, broad, inexpensive harmonic reduction plus transient protection, and it is a good first step. A dedicated harmonic filter tackles harmonics far more aggressively and specifically, at higher cost and size. If a line reactor's harmonic improvement is not enough to meet a limit, the answer is a proper harmonic filter or a low-harmonic drive, not simply a bigger reactor, which would just drop more voltage without proportionally more benefit.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.