Performance
If Roflow feels sluggish, hangs, or seems to use a lot of memory, this page walks through the practical, safe fixes — from a quick restart to tips for keeping big projects and long tasks running smoothly.
Start with a restart
Most temporary slowdowns clear up with a clean restart. A long session — especially one with several big tasks — can leave Roflow holding on to more memory than it needs.
- Wait for any running task to finish, or press Cancel in the chat to stop the agent.
- Fully quit Roflow (don't just close the window).
- Reopen it. Roflow remembers whether you last had the Dashboard or the Code editor showing, so you'll land back where you were.
If Studio was connected, reopen your game in Roblox Studio too so the Studio Bridge reconnects. See Connection Problems if it doesn't link back up.
Roflow and Roblox Studio run side by side, and each uses its own memory. If your whole machine feels slow, restarting Studio as well as Roflow often frees up the most resources.
Close what you're not using
Every open window, project, and playtest keeps using resources in the background. Closing the ones you don't need is one of the fastest ways to lighten the load.
- Extra editor windows and projects. Close Roflow windows and projects you aren't actively working in. You can always reopen a project from the Projects page.
- Leftover playtest windows in Studio. Roflow can stop a solo playtest for you, but ending a multiplayer test is not automatic — you have to close the extra test windows in Studio yourself. Stray test windows keep running and consume memory, so close them when you're done. See Playtesting.
- Editor tabs and the 3D viewport. Close editor tabs you're finished with, and close the 3D Viewport tab when you aren't looking at your scene — it renders your place in 3D and is heavier than a normal text tab.
After a multiplayer playtest, check Roblox Studio for any test windows still open and close them. Forgetting can leave several game instances running at once.
Keep Roflow and the Studio Bridge updated
Running the latest versions is one of the most reliable ways to avoid performance problems, since updates include fixes and improvements.
Roflow app. You can see your installed version on the Settings page in Roflow. Compare it against the current version shown on the Downloads page; if you're behind, download and install the latest build.
Studio Bridge plugin. If the plugin in Roblox Studio is out of date relative to your Roflow app, it stays connected but shows a yellow banner prompting you to update. When you update or reinstall the plugin, fully close and reopen Roblox Studio so the new version loads. See Studio Bridge for the full install-and-connect steps, and Installation for downloading Roflow itself.
Working in very large projects
Big projects and long conversations give the agent more to keep track of, which can make responses slower. A few habits keep things snappy:
- Start a fresh task when you switch goals. A very long back-and-forth carries a lot of history. When you move on to something new, type
/newtaskin the chat to start clean. Your project files and checkpoints are untouched — you're only clearing the conversation. - Condense a long conversation. The
/smolslash command compacts the current conversation so the agent has less to re-read, while keeping the important context. - Watch the context indicator. The expandable task header shows how much of the context window a task is using. When it's getting full, that's a good moment to start a new task or condense. For very long jobs, Roflow also summarizes the conversation on its own so it can keep going without losing earlier decisions.
- Keep the agent focused. A project's
.roflowignorefile tells the agent which paths to leave alone (sensitive and bulky folders like.git,node_modules, andPackagesare ignored by default). Keeping it tidy means the agent isn't sifting through files it doesn't need.
For a smoother approach to large builds overall, break work into smaller pieces — see Building in Stages.
Speed up the agent itself
If it's the agent's responses that feel slow rather than the app, a couple of choices help:
- Pick a lighter model for simple work. The model button in the composer lets you choose a tier. The Fast model is meant for quick edits and uses less of your allowance; Max is the most capable but heavier, so save it for genuinely complex reasoning and debugging. See Usage for how tiers draw on your allowance.
- Give focused context. The more precisely you point the agent at the right files or folders with
@, the less it has to search. See Talking to Roflow.
The agent needs an internet connection to work. If replies are unusually slow or stall, check your network, then see AI Issues.
Ease the load from Studio syncing
While Studio is connected, Roflow syncs your file edits into your open place. If you want to do a burst of heavy local editing without that running in the background, you can pause it: run Toggle Studio Sync from the command palette (or click the Studio indicator in the status bar) to stop live syncing, then toggle it back on to push your changes and resume. The setting is remembered per project. See Studio Bridge.
Check your system meets the requirements
Roflow needs a minimum of about 4 GB of RAM and 500 MB of install space, and an internet connection for its AI features. It runs on macOS (Apple Silicon, M1 or newer, macOS 11 or later) and Windows 10/11 (64-bit). If your machine is at or below the minimum, closing other heavy apps while you work makes a noticeable difference. Full requirements are on the Installation page.
Still running slow?
If none of the above helps:
- Try the other troubleshooting pages: Connection Problems, AI Issues, and Installation Issues.
- Check the FAQ.
- Ask in the Roflow Discord community, linked from the Downloads page.