Phantom Camera for Godot 4: A Cinemachine-Style Camera Addon
A Camera addon for Godot 4. Inspired by Cinemachine.
At a glance
- What is it?
- Phantom Camera is an MIT-licensed Godot 4 addon that adds priority switching, follow modes and animated transitions to the built-in Camera2D and Camera3D nodes. It is aimed at developers who want Cinemachine-style camera behaviour without writing the logic themselves.
- Who is it for?
- Adopt Phantom Camera if your Godot 4.4+ project needs priority-based camera switching, follow modes, or animated transitions between camera positions and you would rather configure that than write it. Skip it if you need offline access to the documentation, since the README points only to phantom-camera.dev, or if your camera logic is simple enough that a script on Camera2D is less to maintain.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 11 days ago.
- What is it written in?
- Mainly GDScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on October 2, 2026, and from our analysis. They are not legal advice.
Editorial analysis
The camera logic Godot leaves to you
Godot ships Camera2D and Camera3D as basic nodes. They provide a viewport transform and little else. Everything that makes a game camera feel deliberate, such as easing toward a target, keeping two players inside the frame, or cutting to a different angle when a boss appears, is left for the developer to script. Phantom Camera is a Godot 4 plugin that fills that gap. The README describes it as a plugin that provides and simplifies common behaviours for the built-in Camera2D and Camera3D nodes, and names the Unity package Cinemachine as its inspiration.
The intended user is a Godot developer who already knows the engine and wants camera behaviour as configuration rather than code. The addon targets Godot 4.4 and above, and the repository's primary language is GDScript, with a C# project file present at the top level. The problem it addresses is not rendering. It is the accumulation of per-project camera scripts that every team writes slightly differently.
Priority, follow modes and transitions
The mechanism is a separate node type, the PhantomCamera, that sits alongside the real Camera2D or Camera3D. The README states that priority determines which PhantomCamera should be active with the Camera2D or Camera3D, and that when a new camera receives a higher priority than the currently active PhantomCamera, the Camera2D or Camera3D will transition to the new one. So the addon owns the decision of which camera is live, and the engine node is the output.
Follow behaviour is a second layer on top of that. The documentation lists three follow modes. Glued sticks to its target. Simple follows the target with an optional offset and damping. Group follows the centre of a collection of targets. The README's own description of the addon mentions reframing itself to keep multiple nodes in view, which is what the Group mode is for.
The third piece is animation between PhantomCamera nodes. The README describes dynamically animating between specific camera positions, meaning other PhantomCamera nodes, on demand. Combined with priority, this gives a workflow where a designer places camera nodes in a scene, sets their follow behaviour, and then triggers switches at runtime. The repository layout reflects the split between the addon and its examples: addons/ holds the plugin itself and dev_scenes/ holds the development scenes used to exercise it.
Installing Phantom Camera in a Godot 4.4 project
The README does not include a step-by-step install section. It links to phantom-camera.dev for documentation and guides, so the commands below are the standard Godot addon layout implied by the repository rather than a quoted procedure. Treat the asset library route as the one to check first.
If you prefer a git checkout, clone the repository and copy the addon directory into your project so that it sits under res://addons/:
git clone https://github.com/ramokz/phantom-camera.git
cp -r phantom-camera/addons/phantom_camera your_project/addons/After the files are in place, enable the plugin from the editor. In Godot, open Project > Project Settings > Plugins and tick the checkbox next to Phantom Camera. The editor should then expose the PhantomCamera node types when you use Add Child Node.
A first real use is to attach a PhantomCamera to an existing Camera2D or Camera3D and point it at a target. Add the camera node to your scene, add a PhantomCamera as a sibling, set its target to the node you want it to follow, and choose the Simple follow mode with damping if you want the movement eased rather than rigid. To switch between two camera positions, place a second PhantomCamera at the new position and give it a higher priority value than the first; per the README, the active camera will transition to it.
The documentation lives off-repository
The clearest limitation is where the knowledge sits. The README is a feature index with links, not a manual. Every substantive explanation, including the priority page and the follow mode pages, points to phantom-camera.dev. The repository itself contains no docs directory. If you work offline, mirror the site or read the source in addons/ instead.
The second limitation is version coupling. The README badge states Godot 4.4 or newer. That is a hard floor, and it means anyone still on Godot 4.2 or 4.3 cannot adopt the current release without moving the engine version first. The plugin is also not a general camera framework. If your game needs a fixed camera, a single follow script, or a custom projection, the addon adds a node layer and a priority system you will not use. Writing twenty lines on Camera2D is the smaller change in that case.
Phantom Camera against Cinemachine and hand-written scripts
The obvious comparison is Cinemachine, the Unity package the README names as the inspiration. The difference is scope and portability. Cinemachine is maintained by Unity and tied to that engine's component model. Phantom Camera reimplements the idea for Godot's node tree in GDScript, so the concepts transfer but the API does not. If you have used Cinemachine, the priority and follow mode ideas will be familiar; the node names and properties are not the same.
The other alternative is a hand-written camera script attached directly to Camera2D or Camera3D. That approach has no dependency, no plugin to enable, and no version floor beyond the engine itself. What it lacks is the priority system and the transition between camera positions, which is exactly the part that is tedious to write and easy to get subtly wrong. Phantom Camera is the better choice when you have several camera states and want them declarative; the script is the better choice when you have one.
Maintenance, licence and upgrade cost
The repository is not archived, and its last push was on 2026-09-21. The most recent tagged release listed is v0.11.0.3 from 2026-07-19, preceded by v0.11.0.2 in March 2026 and v0.11.0.1 earlier that same month. The version numbering, still in the 0.11 line, tells you the API is pre-1.0 and that minor releases may move things. Budget for reading release notes before upgrading rather than assuming drop-in compatibility.
The licence is MIT, stated in the README badge and present as a LICENSE file at the repository root. In practical terms that is a permissive licence, and the repository also carries SECURITY.md, CONTRIBUTING.md and CODE_OF_CONDUCT.md at the top level, which suggests a project set up for outside contributions. This is not legal advice; read the LICENSE file for the actual terms. The upgrade cost is mostly the pre-1.0 churn plus the Godot 4.4 floor, not licensing friction.
Editorial conclusion
Adopt Phantom Camera if your Godot 4.4+ project needs priority-based camera switching, follow modes, or animated transitions between camera positions and you would rather configure that than write it. Skip it if you need offline access to the documentation, since the README points only to phantom-camera.dev, or if your camera logic is simple enough that a script on Camera2D is less to maintain. Before committing, verify your Godot version is 4.4 or newer and check the roadmap milestones for the features you depend on.
Frequently asked questions
How do I use Phantom Camera in Godot 4?
Enable the addon in Project Settings under Plugins, then add a PhantomCamera node next to your Camera2D or Camera3D and set its target. Follow behaviour comes from the follow mode you choose, and switching between cameras is driven by priority.
What is Phantom Camera for Godot?
It is a Godot 4 plugin that provides and simplifies common behaviours for the built-in Camera2D and Camera3D nodes, inspired by the Unity package Cinemachine. It is licensed under MIT.
Is there a Phantom Camera alternative for Godot?
The main alternative is a hand-written script on Camera2D or Camera3D. That removes the dependency and the version floor, but you lose the priority system and the transitions between camera positions, which Phantom Camera handles for you.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/ramokz-phantom-camera)