# --- IDE & System Files --- # Visual Studio Code .vscode/ *.code-workspace
: These contain local data or temporary build files . saves/ (Your personal playtest saves) cache/ (Internal Ren'Py cache) tmp/ (Temporary files)
Setting up a .gitignore for a Ren’Py project is essential for keeping your repository clean, protecting your privacy (by not sharing local save files), and avoiding merge conflicts on auto-generated files. The "Bare Minimum" Ren'Py .gitignore For most small projects, PyTom (Ren’Py’s creator) recommends focusing on compiled files and local user data: gitignore # Compiled script files (Ren'Py regenerates these automatically) *.rpyc *.rpymc
System and IDE metadata. Keeps commits clean for all team members.
When developing a visual novel in , using version control like Git is essential for tracking changes and collaborating with others. However, Ren'Py generates many temporary, local, and auto-generated files that don't belong in your repository. A properly configured .gitignore file ensures your repository stays lightweight and prevents "merge hell" caused by conflicting local data. Why Do You Need a .gitignore for Ren'Py?
Here’s the essential .gitignore template for any Ren’Py project—plus an explanation of why each entry matters.
Cache files are temporary graphics or data caches. Save files belong to players, not your repository. Never track them.