How to Program and Customise a Proffie Saber: Blade Styles, SD Card and Editor

Quick answer: there are three levels of customising a Proffie saber, and only the last needs code. (1) Use the ProffieOS Workbench in a browser to change presets, colours and fonts. (2) Copy sound font folders to the SD card. (3) Edit the config file in the Arduino IDE and upload it, which is the only route that changes blade counts, button behaviour and the blade style code itself. Most owners never need level 3. This page explains what each level can change, how the upload works, and where people go wrong. If you do not yet know what a Proffie saber is, start with what is a Proffie lightsaber.

Which route should you use?

The ProffieOS documentation says exactly this about fonts (accessed 2026-10-06): you can use the Workbench, an on-saber Edit Mode on recent versions with a particular prop file, a re-flashed config, or simply replace the contents of an existing font folder.

Level 1: the Workbench (no code)

The ProffieOS Workbench is a web app that talks to the board over WebUSB or Bluetooth. According to the documentation it can adjust volume, show battery voltage, trigger clash and blast effects, edit each preset's name, font, track, style and colour, add new fonts you have already placed on the SD card, reorder, duplicate or delete presets, and reset the board to factory settings. Changes save immediately, which is convenient and means you should note the settings you started with.

Practical points:

• WebUSB support depends on your browser. Check the Workbench page for what it supports before you plan around it.
• Bluetooth only works if your saber has a Bluetooth module. See lightsaber apps and Bluetooth.
• The Workbench edits presets that already exist in the firmware. It does not rewrite the blade style code that someone compiled in.

Level 2: the SD card and sound fonts

The SD card holds the sound fonts. A font is a folder of audio files plus a small config file. The Proffie documentation describes the steps as copying the font to the card (either by removing the card or, if the saber supports it, over USB), then telling ProffieOS about the font through the Workbench, an Edit Mode, the config, or by naming the folder to match an existing one so no reconfiguration is needed.

Two pieces of seller guidance that matter in practice (accessed 2026-10-06):

1. Keep folder names short and simple. The documentation suggests eight characters or fewer.
2. On at least one seller's Proffie setup, owners are told to delete presets.ini and presets.tmp before new fonts will appear, and that names are case and punctuation sensitive. Presets edited on the saber are stored in presets.ini, so deleting it also discards those edits. Back it up first (our inference from the two sources, not a tested result).

For what a font contains and where fonts come from, read lightsaber sound fonts explained.

Level 3: the config file and the Arduino IDE

What the config file contains

The config file is split into three sections, by the documentation:

• CONFIG_TOP: hardware settings and global values, including the number of blades (NUM_BLADES) and audio volume.
• CONFIG_PRESETS: each preset combines a font, a track and one or more styles.
• CONFIG_BUTTONS: the physical buttons and their functions. Which button does what is set largely by the prop file you choose, covered in how to use a lightsaber.

What a blade style is

A blade style is code that says how the LEDs should look and react. The documentation describes it as C++ that tells the rest of the program how to behave, built from small functions for things like a spark at the tip when igniting or a strobe. Each preset carries one style per blade, so if NUM_BLADES is 3 (a main blade plus two accent LEDs, for example), every preset needs three styles. A mismatch between the two numbers is one of the most reported compile errors.

Most people do not write styles from scratch. They paste styles generated by a community tool or choose one in a config generator. The documentation names the options: a seller's SD card config, a configuration generator web page, an existing config you adapt, or helper tools such as Fett263's style library and ProffieConfig.

Setting up to upload

The setup in the documentation (accessed 2026-10-06) is:

1. Install the Arduino IDE.
2. In Preferences, add the Proffieboard Board Manager URL given in the docs, then install the Proffieboard plugin from the Boards Manager.
3. Select your board version under Tools, then set the DOSFS option to match the hardware: SD card (SPI) for V2 boards, SD card (SDIO High Speed) for V3 boards.
4. Install the driver for your operating system: a setup program on Windows, udev rules on Linux, nothing extra on Mac.
5. Open ProffieOS.ino, point the CONFIG_FILE line at your config filename, and click Upload.

Do not skip step 3: the documentation gives a different DOSFS setting for each board version, so check the version first.

Before you flash: a checklist

1. Copy the whole SD card to your computer. Keep it unchanged.
2. Save the seller's original config file somewhere safe. If you cannot get it, ask the seller.
3. Write down the board version (V2.2 or V3.9). The wrong board setting is the common error.
4. Check your warranty. Some sellers treat re-flashing as a modification.
5. Charge the battery before you start, per the care guidance in care and charging.
6. Know your blade count and write it next to NUM_BLADES.
7. Change one thing at a time. If it breaks, you know which change did it.

What goes wrong, and what to check

Volume and the usual first tweaks

Volume is a CONFIG_TOP setting, and the Workbench can change it live. Many first-time owners also want a different ignition colour or sound. Both are Level 1 or 2 changes. You do not need a code editor to change either, and doing so keeps you away from the risks of re-flashing.

Limits of this guide

We have not flashed a Proffieboard or used the Workbench ourselves, and this page does not claim hands-on testing. Steps come from the ProffieOS documentation and seller guides accessed on 2026-10-06; those documents change with new releases, so confirm the current wording on the linked pages before you start. Software names are used descriptively and we are not affiliated with them.