That Lurch in the Middle of Your Footage
You're filming a birthday dinner. Candles, warm overhead light, everyone laughing. The shot looks great. Then, about twelve seconds in, the whole frame goes slightly cooler and bluer, as if someone had quietly turned a dial on the mood. Nobody moved. The scene didn't change. The phone just decided the world looked different and corrected for something that didn't need correcting.
This is mid-video white balance drift. It happens because your phone's camera is constantly second-guessing itself.
Auto White Balance Is a Continuous Negotiation
White balance is the camera's attempt to make white objects look white regardless of the light source. Candle flame sits around 1800K on the colour temperature scale. Overcast daylight is near 6500K. A fluorescent office closer to 4000K. The camera reads the dominant colour cast and subtracts it, so your subject looks natural rather than orange or blue.
Set white balance manually and that reading happens once, then locks. Auto white balance (AWB) is different. It samples the scene continuously, recalculates, and adjusts. For still photography this is mostly fine: each frame is independent, and a small shift between shots is invisible. Video is a sequence of frames playing at 24 or 30 per second. A recalculation that shifts the colour temperature by even 200K becomes a visible lurch in playback.
The recalculation loop is the engine of the problem. Your phone's image signal processor (ISP) runs an AWB algorithm that analyses the average colour in the frame, the highlights, and sometimes specific reference regions it identifies as likely-neutral (grey walls, white clothing). It then pushes a correction. On most flagship Android phones and iPhones, this loop runs continuously throughout recording, because the software was originally tuned for responsiveness, not narrative consistency.
Why It Fires When Nothing Changed
So if the scene is static, why does the algorithm suddenly decide to re-correct?
A few specific triggers. They're more subtle than you'd expect.
First: subject movement within the frame. Someone at your dinner table leans into the shot wearing a bright red jumper. The ISP now sees significantly more red in the frame and interprets this as a warm colour cast, so it cools the image to compensate. The light source hasn't changed at all. One person shifted, and the camera panicked.
Second: exposure changes. Your phone adjusts exposure continuously, and exposure and white balance share data in most ISP pipelines. If the scene gets slightly brighter (a passing car's headlights sweep across a window in the background, briefly), the exposure algorithm adjusts, the tonal distribution of the frame changes, and the white balance algorithm reads the new tonal data and fires a correction.
Third: mixed light sources. This is the sneaky one. In a room lit by both warm tungsten pendants and cool daylight from a window, the algorithm is genuinely confused. It has no stable reference. It keeps sampling, keeps finding slightly different answers, and keeps nudging the correction back and forth. The result isn't a single lurch but a slow, seasick drift over the course of a shot.
Fourth: the algorithm's own smoothing lag. Most modern AWB implementations don't jump to the new value instantly. They interpolate toward it over a number of frames to avoid harsh cuts. On iPhones running default video mode, this smoothing window is roughly 30 to 60 frames. A correction triggered by a brief event (a phone screen lighting up in the background for two seconds) produces a slow colour drift that continues for one to two seconds after the triggering event has already ended. You watch the footage back and you can't even identify what caused it.
The Worked Example That Makes This Concrete
Picture two people, Priya and Marcus, filming a five-minute interview in the same living room on the same phone model, one week apart.
Priya films in the afternoon. One light source: a floor lamp in the corner. The interviewee sits still. The AWB algorithm samples consistently, finds a stable warm reading around 3200K, locks onto it within the first few seconds, and barely moves. Uniform colour, start to finish.
Marcus films at dusk. Daylight is fading through the window behind the interviewee, slowly shifting from 5500K toward 3800K over the course of the interview. The floor lamp is the same. But now the ISP is watching two competing light sources trade dominance over five minutes. It chases the shift. The footage starts warm-neutral and ends noticeably orange, because the algorithm eventually gave up on the window and leaned into the lamp, in slow, uneven steps. Same phone, same room, completely different result.
The variable isn't the hardware. It's the stability of the dominant light source.
The White Balance Lock Does Less Than You Think
The standard advice is: lock your white balance before you record. True, and also not quite enough on its own.
A common assumption is that locking white balance via a camera app's manual mode is equivalent to what a dedicated video camera does. It isn't, and this distinction matters more than most guides admit. On many Android phones in third-party apps like Filmic Pro or Camera FV-5, a manual white balance lock genuinely freezes the ISP's correction, applying a fixed offset regardless of what the algorithm computes. That's a true lock.
On iPhones using the native Camera app, tapping and holding to lock AE/AF also locks white balance, but the implementation has historically been softer than professional video apps: some users and videographers report the lock drifting slightly under mixed light conditions, particularly in longer recordings. Whether this is a true lock or a strongly-biased AWB is a distinction Apple hasn't formally documented, but the practical behaviour is observable.
The more reliable approach for controlled work: use a dedicated video camera app that exposes white balance as a Kelvin value you set manually. Set it before you roll. If the light changes mid-shoot, stop the recording, adjust, and cut. Trying to fix a mid-shot AWB drift in post means either colour-grading frame by frame or accepting a visible shift. Neither is fun, and one of them is a lie you tell yourself at midnight.
Found your footage doing this? If you can isolate the moment the drift starts and identify what changed in the frame at that exact second (a person entering, a light flickering), you've found your trigger. That's genuinely useful, because it tells you whether you have a light-source problem or a subject-movement problem, and those have different fixes.
The Hardware Isn't the Villain Here
It's tempting to blame the phone. But continuous AWB isn't a flaw in isolation. In point-and-shoot mode, filming your dog running through the garden, you absolutely want the camera to chase the light as you move from shade to sun. The problem is that the same default that saves your holiday snaps is actively hostile to narrative video work.
Professional video cameras default to manual white balance because they assume the operator knows the difference. Smartphone cameras default to automatic because they assume the operator doesn't want to think about it. Both assumptions are correct for their intended user. The tension shows up when someone who does care about colour consistency reaches for their phone because it's the camera they have.
The ISP is doing exactly what it was designed to do. It just wasn't designed with your birthday dinner in mind.
The Actual Fix Is Simpler Than It Feels
Lock it before you press record. Set the white balance in Kelvin if your app allows it: 3200K for warm indoor tungsten, 5600K for daylight, around 4000K for mixed office fluorescent. Don't rely on the tap-to-lock in the native app if you're doing anything longer than thirty seconds or shooting in mixed light.
And if you're shooting something that actually matters, do a ten-second test clip first. Play it back before you commit. A drift that takes twelve seconds to appear will appear in your test clip, and you'll catch it before it ruins the real take.
The phone in your pocket is a remarkable imaging device with one deeply inconvenient reflex: it wants to chase the light. The job, sometimes, is simply to tell it to stay put.