Tesla .fseq Files, Explained

Every custom Tesla light show is two files on a USB drive: a song, and a .fseqfile that tells the car what to do with its lights. Here's what's actually inside that file, the exact rules Tesla enforces, and why hand-built sequences so often fail.

What a .fseq file actually is

FSEQ stands for Falcon SEQuence— a binary animation format from the xLights / Falcon Player ecosystem, the software world of synchronized Christmas-house displays. When Tesla added custom light shows (software v11, holiday 2021), it adopted this format rather than inventing one, which is why the classic authoring path runs through xLights and Tesla's own light-show GitHub repo.

Inside, the file is beautifully simple: a small header, then a grid of numbers — one brightness value (0–255) for every light channel on every frame. At Tesla's recommended 20 ms frame time that's 50 frames per second, each frame saying "headlights this bright, fog lights this bright, left signal this bright…" There's no audio inside the .fseq — the car plays your separate, matching-filename audio file and steps through the frames in lockstep, which is why an audio file at the wrong sample rate (48 kHz instead of 44.1 kHz) makes a show drift out of sync.

The rules Tesla actually enforces

When you pick a show, the car validates the file before playing it. The requirements:

• Format version: FSEQ v2, uncompressed. This is the classic trap — xLights defaults to compressed output, and Tesla rejects it. In xLights the setting is FSEQ Version: V2 Uncompressed.
• Channels: exactly 48 for a single car. A sequence exported with a different channel count fails outright.
• Frame timing: step time of at least 15 ms; Tesla recommends 20 ms (50 fps).
• Length: up to 4 hours technically — but shows people actually watch run 1–5 minutes.
• Audio pairing: a .wav or .mp3 with the same filename as the .fseq, in a root-level LightShow folder. 44.1 kHz keeps sync.

Channels: why model matters

Each of the 48 channels maps to a piece of hardware — headlight elements, signature strips, fog lights, turn signals, tail lights, plus closures like windows, mirrors, trunks, and (on Model X) the falcon doors. The format is identical across models, but the hardware behind each channel isn't: the channel that drives a Model 3's fog light corresponds to different equipment on a Cybertruck, which has that full-width light bar instead. A sequence choreographed for one model will technically playon another — it'll just light the wrong things at the wrong times. That's why serious shows are built (or rebuilt) per model.

Closures deserve extra respect: channels can physically move doors, windows, and mirrors. Well-built shows stagger those movements and respect travel time rather than slamming everything at once — it's the difference between choreography and abuse of hardware.

The two ways to make one

The xLights route:download Tesla's official xLights project files, learn the sequencer, and hand-place effects across the timeline. Full creative control, and genuinely hours of work per song — the community estimate for a polished show is an evening at minimum, and the export settings above have to be exactly right or the car rejects the file.

The browser route: the builder analyzes your song and generates the choreography — beat-synced, per-model, closure-safe — in minutes, with a 3D preview of your exact car before you export. The export is a correctly-formatted, validation-passing .fseq paired with correctly-named audio, and in Chrome/Edge it can write the USB drive for you, verified byte-for-byte. Your first export is free.