WindowsmacOSLinux

Where Does Furnace Save Modules and Instruments?

Furnace saves .fur modules where you choose, with config and demos next to the install or home folder.

Last updated

Furnace asks where to save each .fur module. There is no forced song library. Most users keep a tunes folder in Documents. Instruments (.fui), wavetables (.fuw), and samples travel the same way, either beside the song or in a shared folder.

Config and recent file lists follow the OS convention. The portable zip on Windows keeps things next to furnace.exe. Package installs on Linux behave like normal desktop apps with config in the home directory.

Where Furnace stores this, by platform

Windows
Documents (user chosen .fur files)

Portable zip install. Songs save wherever you pick. Config sits beside the executable unless you use an installed package build.

macOS
~/Documents (user chosen .fur files)

Drag install to Applications, keep songs outside it. Config follows macOS Application Support conventions. Demos live in the download bundle until you copy them out.

Linux
~/Documents (user chosen .fur files)

Native or Flatpak builds both prompt for save location. Flatpak config sits under ~/.var/app/org.tildearrow.furnace. Back up .fur plus .fui and .fuw files together.

Frequently asked questions

What files do I need to back up a Furnace song?

Keep the .fur module plus any external .fui instruments, .fuw wavetables, and samples if you used separate files. A song with everything embedded needs only the .fur file.

Can Furnace open DefleMask .dmf files?

Yes. Furnace loads .dmf from all DefleMask versions and can save back to .dmf as well as its own .fur format. Save a copy as .fur first so you keep Furnace specific features.

Notice an outdated path? Let us know.