
Fox3 Livery Share · add-on for Fox3 DCS server owners
Share a livery once. Every pilot in your squad gets it in the right folder, with the right name, before the next sortie. Nothing to install. Works in Chrome and Edge.
Someone paints a gorgeous new skin for the F-16 and posts a zip in Discord. Half the flight unzips it into the wrong folder. Two pilots never download it at all. Come Friday night, the formation shot has three default gray jets in it, and the question that never dies is back: "why can't I see your skin?"
DCS only shows a custom livery to pilots who have the exact same files, in the exact same folder, on their own PC. Keeping a whole squad in step by hand is a part-time job.
Livery Share gives your squad one shared pool of liveries, tied to your squad's Discord server. Anyone in that Discord server is a member. Members sign in with Discord at skin-sync.fox3cloud.com, point the page at their DCS folder once, and from then on the squad's liveries simply show up on their PC.
Your Discord server is the squad. No separate accounts to create, no invitations to manage. If someone is in your Discord, they are in.
Any member can share a livery from their own DCS folder. Everyone else receives it on their next check.
Liveries are tracked file by file. When the painter tweaks one texture, members download that one texture, not the whole 300 MB livery again.
The pool page shows every livery, who shared it, how many members have it installed, and how many times it has been downloaded. The squad admin finally gets a real answer to "why can't I see your skin": because Dave has not synced since Tuesday.
Plenty for a full set of liveries across several aircraft.
At skin-sync.fox3cloud.com, then open Sync in browser.
Pick Saved Games\DCS (or DCS.openbeta). Your browser asks once whether the page may view and edit that folder. Choose Edit files.
The squad's liveries start arriving. The page checks again every ten minutes while it stays open, or whenever you click Sync now.
Chrome and Edge work out of the box, and Edge is already on every Windows PC. Brave users turn on one setting first (brave://flags/#file-system-access-api), and the page tells them so. Firefox and Safari cannot write to a folder from a web page, so they cannot run the sync page; the rest of the site works in any browser.
Prefer something that runs in the background without a browser tab? There is a small Windows agent too. It sits in the system tray, syncs on its own, and can run side by side with the browser page.
Any livery that works for you in DCS can be shared. It lives where it always has, Saved Games\DCS\Liveries\<aircraft>\<livery name>, with its description.lua. Open the sync page, scroll to Share your own liveries, and click Share next to it. The page reads the files, uploads only what the pool does not already have, and the row changes to shared v1.
A livery name can be used once per aircraft in a pool, and only the person who shared a livery can update it. Changed it since? The row offers Upload new version, and the squad gets the update on their next sync.
By default members get everything in the pool. Anyone can untick a livery, or a whole aircraft they do not own, and the page leaves those alone.
This matters to us more than any feature.
Liveries\<aircraft>\<livery> folders that it created itself. It marks those folders so it knows which ones are its own. A livery you made by hand is never touched.Saved Games\DCS\.flss-trash\<date>\ and kept for 14 days.You run the pool from the same site. You can see the full picture of who has which livery and which version, remove a livery from the pool, and limit sharing to a Discord role if you want only your painters to publish. Members who leave your Discord server stop receiving updates; what is already on their PC stays theirs.
A shared pool is only as good as what goes in it. If your squad wants a custom livery of its own, with your patch, your tail code and your colors, Fox3 builds them. Send us a photo or an idea and we deliver the finished skin, ready for the pool so the whole squad is flying it by the weekend. See custom liveries
No. They sign in to the Livery Share site with Discord. Being in your Discord server is the membership.
Yes. Add each DCS folder on the sync page. Liveries go into every folder that is ticked.
The page can only see the folder you pick, only while you allow it, and your browser can revoke that at any time. Inside the folder it writes only to livery folders it created, and anything it replaces is kept for 14 days. See "What it will never do" above.
DCS holds livery files open, so close it before syncing and start it again afterward. DCS reads liveries at launch; a sync while it is running will not show up until a restart.
Untick it on the pool page. Untick the aircraft heading to skip every livery for a module you do not own.
No. A folder the page did not create is never modified. If names collide, you see a conflict and decide.
Up to 400 files and 4 GB per livery, inside the squad's 50 GB.
The pool stays available to the end of the paid period. After that members keep their local files and simply stop receiving updates. Re-subscribe within 90 days and the pool comes back with everything in it.
Google Chrome and Microsoft Edge. Brave works after turning on one flag. Firefox and Safari cannot write to your DCS folder from a web page, so for those pilots the background agent is the way.
The server owner adds Livery Share to their Fox3 account for $9.99 a month. The pool is tied to the Discord server linked to that account, so everyone in it is a member from day one. If your Discord server is not linked yet, open a ticket and we link it for you.