The fastest way to reuse a scene in Godot
To import a scene into another scene in Godot, you instance it: drag the scene file from the FileSystem panel into the editor viewport, or right-click the scene file and select "Instance Child Scene". Godot then creates a node that points to that scene file. When you run the game, that node loads the entire scene — all its nodes, scripts, and properties — as a child of wherever you placed it.
This is different from copying and pasting nodes. When you instance a scene, you create a live link to the original file. If you change the original scene, every instance of it updates automatically. This is how you build games in Godot without duplicating work: you make a scene for a door, a scene for an enemy, a scene for a button, then instance them into your level.
Key Takeaways
- Drag a scene file from the FileSystem panel into the viewport to instance it as a child node in your current scene.
- Instances are live links to the original scene file, so changes to the original update every copy automatically.
- You can override properties on individual instances without changing the original scene file.
- Instances appear in the Scene tree with a small chain-link icon, making them visually distinct from regular nodes.
- To break the link and convert an instance to regular nodes, right-click it and select "Make Sub-Scenes Unique".
Instancing a scene by dragging
Open the scene you want to add another scene into. This is your main scene — the one that will contain the imported scene. In the FileSystem panel on the left (the folder icon), navigate to the scene file you want to import. The scene file will have a .tscn extension.
Click and drag that .tscn file directly into the viewport or into the Scene tree on the right. Godot will create a new node at that location that represents the entire scene. The node appears in the Scene tree with a small chain-link icon next to its name, showing it is an instance rather than a regular node.
If you drag into the viewport, the instance appears at the mouse position. If you drag into the Scene tree, it becomes a child of whichever node you drop it on. Either way, the instance is now part of your scene and will load when you run the game.
Instancing a scene through the right-click menu
Right-click the scene file in the FileSystem panel. A menu appears with several options. Select "Instance Child Scene". A dialog box opens asking you to choose a node in your current scene to be the parent of the instance. Click the node you want, then click "Create".
This method is slower than dragging but gives you explicit control over which node becomes the parent. It is useful when your scene tree is complex and you want to make sure the instance goes in exactly the right place in the hierarchy.
Overriding properties on individual instances
Once you have instanced a scene, you can change properties on that specific instance without touching the original scene file. Click the instance in the Scene tree to select it, then look at the Inspector panel on the right. Any property you change here affects only this copy.
Properties you override appear in bold text in the Inspector. If you want to revert a property back to what the original scene has, right-click the property name and select "Reset". This is how you reuse the same scene many times with small variations — instance a door ten times, then change the position, rotation, or color of each one individually.
Be careful: if you change the original scene file after overriding properties on instances, the instances keep their overrides. The original properties update, but your custom values stay in place. This is usually what you want, but it means instances can drift out of sync if you are not paying attention.
When instances update and when they do not
If you edit the original scene file — add a new node, change a script, adjust a sprite — every instance of that scene updates immediately. You do not have to reload anything. This is the power of instancing: you fix a bug in the original scene, and it is fixed in all fifty copies at once.
However, if you override a property on an instance (like changing its position or color), that override stays even when the original scene changes. The instance inherits the new structure and scripts from the original, but keeps your custom property values. If you want an instance to go back to matching the original exactly, delete the instance and create a new one.
Breaking the link with "Make Sub-Scenes Unique"
If you instance a scene and later decide you want to edit this copy independently without affecting the original, right-click the instance in the Scene tree and select "Make Sub-Scenes Unique". Godot converts the instance into regular nodes, breaking the link to the original file.
After you do this, the instance is no longer a live link. Changes to the original scene will not affect this copy. The chain-link icon disappears from the Scene tree. Use this when you have instanced a scene but need to make major changes to just one copy, or when you want to save a customized version as a new scene file.
Saving an instance as a new scene file
If you have customized an instance heavily and want to save it as its own scene file, right-click the instance in the Scene tree and select "Save Branch as Scene". Choose a name and location, and Godot creates a new .tscn file with that instance's current state.
This new scene file is independent. It no longer points to the original scene. You can now instance this new file elsewhere, or edit it further. This is useful when you have made an instance so different from the original that it makes sense to treat it as its own reusable scene.
Frequently Asked Questions
Can I instance a scene into itself?
No. Godot will not let you create a circular reference where a scene instances itself, directly or indirectly. If you try, you will get an error. This prevents infinite loops that would crash the editor.
What happens if I delete the original scene file after instancing it?
The instances will break. They will show an error in the Scene tree and will not load when you run the game. Always keep the original scene file as long as you have instances of it in use.
Can I instance a scene that is already inside another scene?
Yes. You can nest instances as deeply as you want. A scene can instance another scene, which instances a third scene, and so on. This is how you build complex games — small reusable pieces combined into larger pieces.
Do instances take up more memory than copied nodes?
No. Instances are actually more efficient. Godot loads the scene file once and reuses it for every instance. Copying and pasting nodes creates separate copies in memory, which uses more space.
How do I see what nodes are inside an instance?
Double-click the instance in the Scene tree, or right-click it and select "Edit". The editor opens the original scene file so you can see and modify its structure. When you are done, click the back arrow or the scene name at the top to return to your main scene.