What is a prefab used for?
A prefab supplies reusable content for the worldbuilding editors. The official material establishes the documented feature, while the dated gameplay examples help show how that feature appeared in a particular build. Keeping those two evidence types together makes it easier to separate a confirmed mechanic from an assumption based on another game. It can reduce repeated manual setup when you need templates or configured pieces of a world.
A difference between those versions can explain apparently conflicting instructions without proving that one source is universally correct. If a step or value is not demonstrated in the collected sources, treat it as unverified and check a current developer update before relying on it. The housing material gives a concrete example: a prefab can provide the House template used by a functional House POI. This does not mean that every prefab is a complete saved world.
A reusable component and the entire world's state are different scopes. The collected material does not establish one universal package structure, so this guide does not claim that every export contains all referenced content or behaves like a full save backup. This keeps unrelated editor choices from obscuring what changed. It also gives you a clearer basis for describing a reproducible result to other players, without turning one observation into a guaranteed rule for every save or build.
Is import and export officially confirmed?
The developer's July interview describes prefab import and export as part of the toolset. The official material establishes the documented feature, while the dated gameplay examples help show how that feature appeared in a particular build. Keeping those two evidence types together makes it easier to separate a confirmed mechanic from an assumption based on another game. Official launch material also names prefabs among the content intended for Steam Workshop sharing.
A difference between those versions can explain apparently conflicting instructions without proving that one source is universally correct. If a step or value is not demonstrated in the collected sources, treat it as unverified and check a current developer update before relying on it. These independent contexts support the existence of prefab reuse without proving a specific modern sequence of interface buttons. The distinction matters when your goal is a reliable procedure.
A feature announcement establishes capability at a broad level, while a reproduced workflow establishes the exact steps and conditions. The collected sources provide the former more clearly than a successful current-version round trip from export to import. This keeps unrelated editor choices from obscuring what changed. It also gives you a clearer basis for describing a reproducible result to other players, without turning one observation into a guaranteed rule for every save or build.
Start with the default content relationship
The June 15 update added an option for default prefab content during world creation. The official material establishes the documented feature, while the dated gameplay examples help show how that feature appeared in a particular build. Keeping those two evidence types together makes it easier to separate a confirmed mechanic from an assumption based on another game. That helps new players avoid manually defining every supporting template before beginning a settlement.
A difference between those versions can explain apparently conflicting instructions without proving that one source is universally correct. If a step or value is not demonstrated in the collected sources, treat it as unverified and check a current developer update before relying on it. It also explains why earlier tutorial recordings can involve more editor work than later ones. Default content and imported content serve related purposes, but they are not evidence for the same distribution mechanism.
Starting a world with provided templates does not demonstrate downloading an external package or subscribing to a Workshop item. Learn what the supplied content configures before treating every reusable element as an independently transferable whole world. This keeps unrelated editor choices from obscuring what changed. It also gives you a clearer basis for describing a reproducible result to other players, without turning one observation into a guaranteed rule for every save or build.
Can imported content be edited?
The June 18 Patch 6 notes document editable imported content. The official material establishes the documented feature, while the dated gameplay examples help show how that feature appeared in a particular build. Keeping those two evidence types together makes it easier to separate a confirmed mechanic from an assumption based on another game. That supports treating prefabs as a starting point for further editor work rather than assuming they are always permanently locked objects.
A difference between those versions can explain apparently conflicting instructions without proving that one source is universally correct. If a step or value is not demonstrated in the collected sources, treat it as unverified and check a current developer update before relying on it. The patch date still matters when comparing recordings that show different behavior. Editing a visual element is also different from changing the underlying simulation relationship.
A house's artwork, its House template and the placed POI each play a role. When reusing content, inspect what is actually configured instead of assuming that its appearance proves it is functionally connected to your new city's systems. This keeps unrelated editor choices from obscuring what changed. It also gives you a clearer basis for describing a reproducible result to other players, without turning one observation into a guaranteed rule for every save or build.
How does Steam Workshop fit in?
The October launch announcement identifies worlds, prefabs and custom sprites as planned sharing categories. The official material establishes the documented feature, while the dated gameplay examples help show how that feature appeared in a particular build. Keeping those two evidence types together makes it easier to separate a confirmed mechanic from an assumption based on another game. This is a distribution and sharing context for reusable creations.
A difference between those versions can explain apparently conflicting instructions without proving that one source is universally correct. If a step or value is not demonstrated in the collected sources, treat it as unverified and check a current developer update before relying on it. The broader code-modding framework is a separate future topic and should not be presented as a requirement for every prefab. The collected materials do not demonstrate a current publish, subscribe, download and import sequence end to end.
They also do not justify inventing Workshop item links or claiming that every announced category is already usable in a particular preview build. Follow the current official integration information when you need exact distribution instructions. This keeps unrelated editor choices from obscuring what changed. It also gives you a clearer basis for describing a reproducible result to other players, without turning one observation into a guaranteed rule for every save or build.
Which details should you avoid guessing?
No verified file extension, storage directory or universal import-button path is established here. The official material establishes the documented feature, while the dated gameplay examples help show how that feature appeared in a particular build. Keeping those two evidence types together makes it easier to separate a confirmed mechanic from an assumption based on another game. Older development logs about selection and pattern workflows should retain their historical context rather than becoming current instructions by assumption.
A difference between those versions can explain apparently conflicting instructions without proving that one source is universally correct. If a step or value is not demonstrated in the collected sources, treat it as unverified and check a current developer update before relying on it. A plausible-sounding filename or menu label would still be an unsupported addition. For practical reuse, identify the content's intended role and the editor systems it depends on.
A housing component belongs in a settlement with the relevant POI and faction relationships, while custom artwork does not automatically define its behavior. If an import fails, report the build, source content and observed result instead of relying on an unverified universal repair recipe. This keeps unrelated editor choices from obscuring what changed. It also gives you a clearer basis for describing a reproducible result to other players, without turning one observation into a guaranteed rule for every save or build.
Sources and verification
This answer cross-checks developer and Steam material against independent reporting or gameplay footage. Details from older demos are identified as historical because interfaces and availability can change between builds.