Is FSD worse at night?
Darkness, oncoming headlights, and unlit rural roads are a different problem than the daytime footage most reviews show.
Coverage by software era
How much footage exists for this scenario in each build. Eras with fewer than 3 matching videos are marked — they are anecdotes, not evidence of a trend.
| Version | Moments | Failures | Highlights | Videos | |
|---|---|---|---|---|---|
| v9 | 22 | 10 | 12 | 1 / 11 | thin sample |
| v10 | 126 | 36 | 90 | 7 / 55 | |
| v10.69 | 7 | 2 | 5 | 3 / 38 | |
| v11.4 | 20 | 5 | 15 | 1 / 35 | thin sample |
| v12.5 | 50 | 17 | 33 | 3 / 24 | |
| v14 | 6 | 1 | 5 | 2 / 5 | thin sample |
| v14.1 | 27 | 2 | 25 | 1 / 14 | thin sample |
Watch it happen
Worst first, newest builds first within each severity. Every card opens YouTube at the moment.

Nav/FSD was about to turn left the wrong way onto a one-way road; he disengages and calls it the worst mistake he has seen.

At the daily work-route lane-selection spot, the car overcorrected left into a turnaround lane instead of properly positioning for the upcoming left turn.

On nighttime dirt/unmarked roads, FSD degrades and repeatedly tries to pull over or turn off rather than continue, a bug Chris says is blatant and ruins this part of the drive.

He got pulled over: Beta stopped at the light, but he hit the accelerator through what he thought was all-way blinking red while the officer had blinking yellow; no ticket after he explained FSD testing.

He disengages because the car was about to enter a do-not-enter drive-thru the wrong way.

He takes over because he does not want the planned right turn and manually puts the truck on the highway for end-to-end testing.

At a dead end the truck stops and will not proceed, so he manually turns it around after noting rear-wheel steering was active.

After an odd move into a right turn lane, Chris took over because he did not actually want to enter the highway.

Emergency vehicle stopped on the right; he moves over for legal move-over and counts it as a disengagement because the car only slows for emergency lights at night and will not change lanes away.

He accidentally disengaged by putting pressure on the wheel so Autopilot would not nag while entering/using the highway.

While trying to turn around with someone behind, driver takes over.

When Chris wants to go straight, beta enters the left turn lane and would turn left, so he disengages and reports it as a strange random lane decision.

On an unprotected left after a fast reroute the maneuver is not good at all and he takes over because it seemed about to mess up.

At a right turn with 50–60 mph cross traffic, Chris hit the brake and disengaged because the car kept creeping too far out; the other car turned right with no turn signal.

Confused by a median (shown purple) while trying to turn left, FSD turns itself off; after waiting for traffic he re-enables and it slowly continues.

It treats a light as a red light and does not see it is blinking, so he takes over and goes through.

He declares the Tesla Challenge a fail because he intervened, while noting Autopilot still lane-keeps and sees well at night.

Without a front bumper camera, the car parked a huge spot but got extremely close to the curb.

While parking, the car got extremely close to a cop car before continuing, with Chris reacting that it nearly hit it.

On a left turn after a stop sign the truck again cuts too sharp and is briefly slightly on the wrong side of the road with no other vehicles present.

On a second Michigan left the truck turns too far left, briefly goes off the road onto the shoulder, then self-corrects; he reports the incident.

Car begins slowing for people walking in the road at night with no reflective gear before the driver sees them; driver moves foot toward the brake but does not intervene.

After solid night roundabout performance, the car treated something that was not a driveway oddly, prompting him to turn around.

On the return direction where night Autopilot had worked, daytime Autopilot is hard to get and then appears set to take the car right off the edge.

He reacts with alarm after nearly missing a person standing on a dark corner near the road, though the person was not crossing.

An older FSD version drove too close to a person walking a dog at night, and the human driver took over to steer away.

Car slowed/stopped at a train crossing after it no longer needed to stop; Chris pushed it through with someone behind.

Car began stopping for a blinking yellow light; Chris intervened by reporting it as incorrect behavior.

While routing was still loading on spotty dirt-road internet, the car took a different path than intended, so Chris manually turned around.

It fully stops for a blinking yellow (says stopping for traffic control) rather than proceeding cautiously; he says the few instances seen on Beta 9 got blinking yellows wrong every time vs mixed results on 8.2.

At a stop sign it creeps for visibility then proceeds; when the light turns yellow he intervenes and later turns FSD back on.

After setting home as destination it goes rogue into a dirt parking lot; he re-engages FSD and it aggressively takes the exit.

A driver behind blinks headlights to urge a lane change the car does not understand; then a bad merge interaction with a hesitating vehicle leads him to take over so as not to make the other driver uncomfortable.

He presses the accelerator after the car speeds up next to another vehicle and then just sits there instead of completing the pass.

Chris stated zero interventions for the drive and that he had not intervened, while concluding brake stuttering appears addressed/gone or greatly reduced.

After changing intent to turn right on red, FSD completed the stop for the prior straight path and did not proceed into the right turn immediately.

When a slow vehicle put on a turn signal and turned at the last second, FSD immediately proceeded, correctly judging no interaction.

On green with a car approaching from the left, FSD proceeded without any hint of brake stabbing/stuttering.

In a school zone the car briefly showed the correct speed limit then changed back to the wrong higher limit while still in the zone.

On a 55 mph road by his house with no speed-limit signs, the nav/speed display flips between 25 and 55 mph.

Creator's own Mad Max clip shows 70 mph in a 55, then still requires a full zero stop at a clear empty stop sign late at night.

The same night pedestrian clip on newer FSD detected the person earlier and moved over earlier, validating the fix.

A Canada Tesla clip shows FSD going 75 mph in a 50 mph zone, described as racing down the street.

On a second try going the long way around, the car did not hesitate at an empty yield and executed a perfect full circle; Chris then took over to continue home.

While driving manually with ultrasonics covered, a nearby storage container was not warned by ultrasonics but appeared on the occupancy network visualization.

With ultrasonics blocked, beta still drove onto the street while one taped sensor showed a red visualization the car appeared to ignore.

Chris taped over the ultrasonic sensors, got park assist unavailable, and still successfully enabled FSD beta in his driveway.

Car still drives well in very dark conditions while showing the common night-time 'Full Self-Driving may be degraded' message on back roads.