---
title: Publish and update an X4 mod on Steam Workshop
summary: WorkshopTool, an isolated release folder, and publishx4 versus update.
section: tools
kind: guide
status: reference
updated: 2026-10-27
tags: ["X4","modding","workshop"]
sources: ["https://wiki.egosoft.com/X%20Rebirth%20Wiki/Modding%20support/Steam%20Workshop%20for%20X%20Rebirth%20and%20X4/"]
---
## Preparation


Use X Tools, Steam ownership of X4, an extension folder with `content.xml`, and a PNG/JPG preview. Run the installed WorkshopTool without arguments for help:



```powershell
& $WorkshopTool
```



Set `$WorkshopTool` to the executable path first. Prepare and inspect a separate release folder rather than publishing your repository root.



## First publication


Learning command for your independent `wiki_demo`, not for publishing this website:



```powershell
& $WorkshopTool publishx4 -path .\package\wiki_demo -preview .\preview.png -buildcat
```



`-buildcat` packs game content. The tool asks for upload confirmation and writes the Workshop ID to `content.xml`; retain it. Check item visibility separately online.



## Update


Increase your extension version and retain its published ID:



```powershell
& $WorkshopTool update -path .\package\wiki_demo -buildcat -changenote "Adjust the example setting"
```



Expect an existing item to update, not a second item. These commands were not executed here.



## Verify the release


Before upload, compare the package with your plan: only your distributable content, required dependencies and a change description. Afterward inspect the item page and test installation of the downloaded package separately. Record its behavior and save/load result.



The account owner accepts Steam terms. This article describes the process without publishing a mod. Related: [CAT/DAT](wiki:tool-catalog), [versions](wiki:version-catalogs), [manifest](wiki:extension-manifest).