Welcome to the Tesla Light Show xLights guide! You can create and run your own light shows on Tesla vehicles.

A custom show can be run on a supported vehicle by loading it via a USB flash drive. Create and share your shows with others! A single show can be shared and run on any supported vehicle; they are not model-specific. The sequence data is stored in a .fseq file and the music comes from your choice of .mp3 or .wav.

Multiple light show repositories can be found online. A screenshot from TeslaLightShare.io is below.

• Model S (2021+)
• Model 3
• Model X (2021+)
• Model Y
• Running Software v11.0 (2021.44.25) or newer

• Must contain a base-level folder called "LightShow" (without quotation marks and case sensitive).
• The LightShow folder must contain at least 2 files:
  • a show .fseq file
  • a show .mp3 or .wav file (wav is recommended)
• The fseq filename must match the mp3/wav filenames
  • E.g., show1.fseq/show1.wav can exist with show2.fseq/show2.mp3
• Multiple shows can be stored on 1 USB drive (2023.44.25+ Vehicle Software)
• Must be formatted as exFAT, FAT 32 (for Windows), MS-DOS FAT (for Mac), ext3, or ext4. NTFS is currently not supported.
• Must not contain a base-level TeslaCam folder.
• Must not contain any map update or firmware update files.

• Insert the flash drive into one of the front USB, USB-C ports, or glovebox USB port, then wait a few seconds.

• In Toybox, select Light Show and tap Schedule Show.

  

• If the files on the USB flash drive meet the requirements, then the custom shows will be available to select from the drop-down menu.

  

reddit.com/r/TeslaLightShow/

• If the popup title is "Light Show" instead of "Custom Light Show", then the requirements are not being met for the USB flash drive formatting and/or required folder and files.
• Error messages will be provided if the required files exist but there is a problem with the light show sequence file.

• The maximum duration for a custom Tesla xLights show is 5 minutes.
• The maximum number of commands during a custom show is 3500:

  • Any transition of a light or closure contributes towards this command limit. Eg, turning a light on and off is 2 transitions.

  • Within each of the following 3 categories, transitions that happen at the same timestamp will only contribute 1 command towards the overall limit. Therefore, within these categories, it is recommended to align transitions at the same timestamp as much as possible.

    • Boolean light
    • Ramping light
    • Closures

  • In this example, two lights will be turned on and off again, one will be ramped and turn off again, and one closure will start moving. Because they're aligned, this effect only counts as two transitions - One at the beginning, and one at the end of the effect.

    

You can use both the mp3 and wav format (.wav is recommended). Make sure the file is encoded with a sample rate of 44.1 kHz; less common 48 kHz files won't properly sync to the light show.

1. Visit xLights Downloads to download and install the xLights application.

2. Download and unzip tesla_xlights_show_folder.zip, which is the Tesla xLights bare project directory.

   • It is recommended to keep the project directory structure as-is and leave all files in their default locations.

3. Open the xLights application.

4. IMPORTANT: In File > Preferences > Sequences > FSEQ Version, select "V2 Uncompressed".

   

5. In File > Select Show Folder, navigate to and select the unzipped project directory, then select Open.

6. Select the Layout tab to view the Tesla 3D vehicle model.

7. Make sure that the 3D preview checkbox is selected.

   

8. Select the Sequencer tab. For the best editing experience, only the timeline and House Preview are needed.

   

9. Note that the official Tesla Model S .xmodel file includes the superset of lights and closures that are needed for all supported vehicles, and should be used to generate shows for all vehicle types. See light channel locations for information about where the lights are on each vehicle.

An example sequence is provided that can be run on the vehicle and/or opened in xLights. These instructions cover how to open it in xLights.

1. Follow the getting started instructions to set up the xLights project.

2. Download and unzip the example light show: lightshow_example_1_elevator_music.zip or lightshow_example_2_Max_Carlisle_Auld_Lang_Syne_In_the_City.zip.

3. In File > Open Sequence, navigate to the unzipped folder and select the lightshow.xsq example file, then select Open.

4. In the Sequencer tab, double click groups in the timeline to reveal individual left / right control.

   

1. Follow the getting started instructions to set up the xLights project.

2. Select File > New Sequence

3. Select Musical Sequence

4. Navigate to your chosen .wav or mp3 file, select it, then select Open. Note that .wav files may be hidden unless file type is set to xLights Audio Files.

   

5. In the Wizard tab select Custom

6. Change the Frame interval to 20ms then select OK.

   

   Note: any value between 15ms and 100ms is supported by the vehicle, but 20ms is recommended for nearly all use cases. The maximum show size limits do not depend on the frame interval.

7. Select Quick Start and wait for the sequencer to load

8. In the top left of the timeline, select "Group View" in the view selector. You can also choose "Old View" for the pre-update layout.

   

9. If using the recommended "Group View", you can double click the light groups to reveal and hide individual left/right control. Placing light effects in the group object will activate both the left and right light

   

10. If using the old view, double click on "GRP Tesla Model S" to view all channels

    

11. For more information on the workflow of creating xLights sequences, please use existing online resources. The rest of these instructions contain Tesla-specific information for show creators.

A Python validator script is provided to help check if your custom light show sequence meets these limitations, without needing a Tesla vehicle.

For usage, run:

python validator.py lightshow.fseq

macOS users should use this command instead:

python3 validator.py lightshow.fseq

Expected output looks like:

> python validator.py lightshow.fseq
Found 2247 frames, step time of 20 ms for a total duration of 0:00:44.940000.
Used 16.45% of the available memory

Most lights available on the vehicle can only turn on or off instantly, which corresponds to 0% or 100% brightness of an 'Effect' in xLights.

• For off, use blank space in the xLights timeline
• For on, place Turn On; Instant (hotkey: 'F' on your keyboard)

The minimum on-time for boolean light channels to produce light is 15ms, although human eyes will have a hard time seeing anything this short! Minimum on-time or off-time of 100ms generally makes the show more pleasing to look at.

In this example, the Left Front Fog turns on and off 3x:

Some channels can have a slow ramp in the intensity during turn-on or turn-off, to create graceful visual effects:

To command a light to turn on or off and follow a ramp profile, place the effect with the corresponding keyboard shortcut:

The keyboard layout is designed to be easy to use. Note that the effect types are grouped into vertical keyboard rows and sorted by duration.

• Ramping can only prolong the time it takes to fully turn a light on or turn off. It is not possible to command a steady-state brightness setpoint between 0% and 100% intensity.
• If an xLights effect is longer than the ramping duration, then the light will stay at 0% or 100% intensity after it finishes ramping.
• Ramping effects can end early or be reversed before completion, and the light will immediately start following the new profile that is commanded.
• To guarantee that a light reaches the 0% or 100% setpoint, the xLights effect must have a duration at least 50ms greater than the ramp duration. Conversely, to guarantee that a light does not fully reach the 0% or 100% setpoint, the xLights effect must have a duration at least 100ms less than the ramp duration.
• Ramping Channels 4-6 have some unique aspects compared to other lights in order to use them effectively - see notes in Ramping Channels 4-6.

• Left inner main beam, Turn on; 2000 ms, effect duration 1s: causes the light to ramp from 0% to 50% intensity over 1s, then instantly turn off (because of the empty timeline).

  

• Left inner main beam, Turn on; 2000 ms, effect duration 4s: causes the light to ramp from 0% to 100% intensity over 2s, then stay at 100% intensity for 2s, then instantly turn off after 4s.

  

• Left inner main beam, Turn on; 2000 ms for 2.06s, Turn off; 2000 ms for 1.9s, Turn on; 2000 ms for 2.06s: causes light to ramp to 100% intensity, then down close to, but not reaching, 0% intensity, then back up to 100% intensity, then instantly turn off.

  

The following tables and images help show which channels are controlled on each car. Some vehicles have lights that do not exist, or have multiple lights driven by the same control output - see notes in Light channel mapping details for this information.

In custom xLights shows, the following closures can be commanded:

To command a closure to move in a particular manner, place an effect with the following keyboard shortcuts:

• Idle: The closure will stop, unless the closure is in the middle of an Open or Close in which case that movement will finish first.
• Open: The closure will open and then stop once fully opened.
• Dance: Get your party on! The closure will oscillate between 2 predefined positions. For the charge port, Dance causes the charge port LED to flash in rainbow colors.
• Close: The closure will close and then stop once fully closed.
• Stop: The closure will immediately stop.

• For closures that do not support Dance, it's recommended to use Open and Close requests to cause movement during the show.
• It's recommended to avoid closing windows during the show so that music stays more audible. Music only plays from the cabin speakers during the show.
• Closures can only dance for a limited time before encountering thermal limits. This depends on multiple factors including ambient temperature, etc. If thermal limits are encountered, the given closure will stop moving until it cools down. Dancing for ~30s or less per show is recommended.

• All closures have actuation limits listed in the table above. Only Open, Close, and Dance count towards the actuation limits. The limits are counted separately for each individual closure.
• With the exception of windows, closures will not honor Dance requests unless the respective closure is already in the open position. The show creator must account for this by adding a delay between Open and Dance requests. Refer to Closure Movement Durations for more information.
• The charge port door will automatically close if 2 minutes have elapsed since opening.
• Closure commands spaced very close together (eg, 20ms) will not cause much visible movement, and will use up the command limits quickly. Leave reasonable time between commands to see the best effects.

• For Idle, Open, Close, and Stop, there is no minimum xLights effect duration in order for the command to take effect. For example, the following sequence has a liftgate open command with duration of only 1s ahead of the dance that comes later, and this is sufficient to open the liftgate all the way:

  

• For Dance, the xLights effect must persist until the dancing is desired to stop.

• Not all vehicles have all types of lights installed. When turning on/off lights in sync with key parts of the music's beat, try to use lights that are installed on all vehicle variants.
• Not all vehicles have individual control over every light. In these cases, multiple xLights channels are OR'd together to decide whether to turn on a given group of lights. These are outlined in the section below.
• For lights that are controlled by multiple OR'd channels, keep in mind that some shared off-time on all of the OR'd channels is required to cause an apparent flash of the light.

  • This example will cause Aux Park lights to turn on constantly on Model 3/Y:

    

  • This example will cause the Aux Park lights to flash on Model 3/Y (note the blank time between each box compared to the other example):

    

• Side markers are only installed in North America vehicles
• Aux park are not installed in Model 3 Standard Range +
• On Model 3/Y, all aux park and side markers operate together. They will activate during (Left side marker || Left aux park || Right side marker || Right aux park) requests from xLights.
• On Model S, aux park and side markers operate together, but they have independent left/right control. They will activate during the following requests from xLights:
  • Left side: (Left side marker || Left aux park)
  • Right side: (Right side marker || Right aux park)

• For Model S/X:
  • Individual on/off control is supported for each channel
  • Only a single ramping duration is allowed between all 3 channels.
  • The ramping duration for all 3 is defined only by the effect placed in xLights for Channel 4.
• For Model 3/Y:
  • All 3 of these channels are combined into a single output on the vehicle, see light channel locations.
  • The on/off state is OR'd together between all 3 channels: (Channel 4 || Channel 5 || Channel 6).
  • The ramping duration is defined by the effect placed in xLights for Channel 4.
• Because channel 4 acts as the leader for setting ramping duration on all platforms, a ramping effect must sometimes be included on Channel 4 even when Channel 4 is not turned on.

  • In this example, each channel blinks 3x and ramps down after its last blink. Notice how an Turn Off, 500ms effect is added always on Channel 4, even when it's Channel 5 or Channel 6 that were turned on.

    

  • In this example, Channel 4 & 6 ramp up and ramp down again. Notice how Channel 6 has the Turn On; Instantly effect while Channel 4 defines the effect to be Turn On; 1000ms for both channels.

    

• Front fog lights are installed in all vehicles except Model 3 Standard Range +.
• Vehicles without front fog lights will not use any other light in place of front fog lights.

• Rear fog lights are installed in non-North America vehicles, and North America Model X.
• Vehicles without rear fog lights will not use any other light in place of rear fog lights.

• On Model 3 built before October 2020: left tail, right tail, and license plate lights operate together. They will activate during (Left tail || Right tail) requests from xLights - note that the license plate lights xLights channel will have no effect on these vehicles.

All old .fseq files are fully compatible with the new light show update. You only need to convert old show files if you want to edit them with the refreshed XLights configuration.

• Create a new folder for the converted project and copy the old audio file over.

• Close XLights

• Download and unzip tesla_xlights_convert.zip

• Open XLights. In the "Controllers" tab under Show Directory, select "Change Temporarily"

  

• Select the old_tesla_xlights_show_folder in the extracted tesla_xlights_convert folder.

• Open your old .xsq file.

• Select Tools -> Package Sequence and save the .zip file in the new folder.

  

• Reopen XLights and create a new sequence with the song from the new folder.

• Select Import -> Import Effects and choose the .zip file you created earlier.

  

• In "Map Channels" Window, select "Load Mapping" and choose "mapping.xmap" located in the "convert to new format" folder.

  

• Press "Ok", the old sequence will import. It's recommended to use the "Old View" for working with converted files.

  

• Press "Render All" to see the imported effects in the preview.