GDevelop Login and Project Management Basics

A GDevelop login may be part of some workflows, but good project organization should not depend on remembering where one copy lives. A clear local structure, predictable names and regular backups make project work easier to recover and move.

Separate identity from project files

Account access and local project storage are different concerns. Treat your editable project files as assets that need their own organization and backup plan regardless of how you access online features.

Practical checkpoint

Use one main folder per project and keep exports, reference assets and backups in clearly labeled subfolders.

Naming and backup habits

Name scenes, objects and project folders according to their role. Clear names reduce mistakes when you duplicate projects, compare test versions or return to an older build.

Why this matters

For significant changes, create a dated or milestone-based backup before editing core event logic, project settings or extensions.

Troubleshooting access confusion

If a login-related workflow seems disconnected from a local project, first identify whether the problem is account access, file location or the editor state. Solving one category at a time prevents unrelated changes from creating more uncertainty.

Next-step habit

When the project itself will not open, use the common-errors guide rather than repeatedly changing account settings.

Recommended next step

Apply the guide to a copy of a small project first. If you are changing setup or download files, keep the current working project separate and return to the Download section only when you understand the file type you need.