By Godot editorial team · Last verified [date] · Current release [tag]
Figure script-editor. Script workspace with a short GDScript open.
Steps
- Confirm a blank scene plays.
- Select a node and attach a new GDScript.
- Add a
_readyfunction that prints a short message. - Save the script beside the scene and press play.
Official docs show hello-world samples in GDScript and C#. Class reference is built into the editor. C# users should install the .NET Godot build and SDK per upstream docs before switching languages.
Related: first run, Project Manager, export Windows, guides.
Keep the Windows path clear
Prefer one editor location. Keep projects elsewhere. When App Installer is missing, install it from Microsoft, reopen the terminal, and retry winget. When you want a folder you control, take the current the win64 editor zip from GitHub Releases, extract, and run the nested editor executable.
Related cluster pages: releases, GitHub overview, download safe, for this computer, how to install winget, and first hour.
Verify before you change the PC
Match the publisher path github.com/godotengine/godot/releases and the win64 zip pattern, or install via the winget PackageIdentifier. Skip countdown pages. Official homepage and docs remain godotengine.org and docs.godotengine.org for product facts beyond install.
MIT licence text lives in LICENSE.txt on the repository. Official docs state no royalties on the engine itself. Unity and Unreal remain commercial products with their own public licensing pages; do not invent dollar tables when you compare.
After the editor opens
Open the Project Manager, create or import a project outside the editor directory, run a blank scene, then attach a short GDScript. Leave export templates until play works. Update later through the same winget id or zip folder you already trust.
godot gdscript first script in daily use
Keep the editor folder and every project folder on different paths. When a newer stable zip arrives, you replace only the editor folder. Scenes, scripts, and imported assets stay where you left them. That separation is the difference between a calm upgrade and an afternoon of hunting missing files.
Name project folders for the game, not for the engine version. Version control belongs on the project. The editor binary is disposable infrastructure you can reinstall with winget or a fresh win64 zip whenever hardware changes.
Signals from the official docs
Upstream documentation at docs.godotengine.org covers class reference, getting started paths, and export details in more depth than an install page should. Use those pages when you need API behaviour. Use This guide when you need the Windows fetch path, the winget id, or the win64 zip pattern.
Bug reports belong on the GitHub issues tracker for godotengine/godot. Feature questions often already have answers in the class reference that ships inside the Script workspace. Prefer primary sources when a blog post and the docs disagree.
Hardware reality on Windows
Official Windows download text recommends Vulkan 1.0 compatible hardware and lists OpenGL 3.3 as the documented minimum. Integrated graphics vary by driver vintage. A blank viewport after a clean install is usually a driver problem, not a missing second installer from a search ad.
SmartScreen may prompt on the first launch of a newly downloaded executable. Prefer files that arrived through GitHub Releases or winget so the bytes match upstream. The official Windows page notes that executables are code-signed by Prehensile Tales B.V.
What to keep out of the install path
Countdown mirrors, renamed setup wrappers, and pages that invent a newer stable number than GitHub shows are the wrong door. Softonic-style packaging is not a substitute for the win64 zip on the stable tag. If a site asks you to run a helper installer before the editor appears, stop and return to Releases or winget.
Export templates are a second download on the same stable line. They are not a reason to fetch the editor again from a different domain. Install templates when you are ready to ship a Windows build for players, after a blank scene already runs on your machine.
Working rhythm after install
Create a tiny project first. Add a root node, save a scene, press play, then attach a short script that prints on ready. Only after that path is calm should you import large art folders or open Asset Library entries. Large imports hide whether the editor itself is healthy.
Updates should reuse the door you already trust. Winget users upgrade with winget. Zip users replace the extracted folder from GitHub. Mixing three copies across Desktop, Downloads, and Program Files is how people open the wrong binary a month later.
Projects, backups, and other PCs
Back up project directories with git or your usual cloud backup. Reinstalling the editor should not require rewriting scenes when projects live outside the editor folder. Moving to another PC means installing the editor again and copying the project folder; export templates are per machine.
Borrowed or locked-down lab machines may block winget and unfamiliar executables. Prefer a PC you control for a clean path. Fighting policy with a third-party wrapper installer is not a fix.
Windows install habit
Prefer the winget PackageIdentifier when App Installer is present. Prefer the current the win64 editor zip from GitHub Releases when the catalog lags. Extract the zip, then run the editor exe. Vulkan 1.0 is recommended; OpenGL 3.3 is the official minimum.
Safe fetch
Match filenames on the official Godot Releases page. Skip Softonic-style portals. Update through the same door you used to install. Related routes: download-safe, releases, Windows install, and the guides hub.
After install
Open the Project Manager, create or import a project, then open the editor. Succeed on a tiny scene before export templates. Public sentences still say the current release rather than freezing a dotted version in prose.
Operator notes
These pages are independent install notes. Release files stay on GitHub. Upstream docs stay on docs.godotengine.org. Read LICENSE (MIT) on the repo before you redistribute modified builds.
Quick install reminders
- Winget id
the PackageIdentifierwhen App Installer is present. - GitHub
the win64 editor zipwhen the catalog lags. - Extract, then run the win64 editor exe.
- Prefer Vulkan when the GPU supports it.
Release files stay on GitHub. Match the official filename before you run anything.
Frequently asked questions
How do I install Godot on Windows?
Run the winget install command after App Installer is present, or download the win64 editor zip from GitHub Releases, extract the zip, and run the editor exe. Prefer the same door for later updates. Never pin a dotted version in prose.
Do I need to extract the zip?
Yes for the standard Windows build. The win64.exe.zip is a zip archive. Extract it, then run the win64 editor exe. Winget wraps that same Windows product as the PackageIdentifier.
Where do official files live?
Official Windows files live on github.com/godotengine/godot/releases as the win64 editor zip, and in Windows Package Manager as the PackageIdentifier. Match those names and skip renamed wrappers.