Fix a project that opens then crashes
Your project opens and then crashes or freezes? Here's how to fix it, from saving your work to clearing extensions and freeing up memory.
If your Kittl project opens and then crashes, the editor is having trouble handling the design once it's loaded. This is usually caused by a browser issue, low memory, an extension, or a heavy project. Most cases clear up with the steps below.
What crashing can look like
A project that opens then crashes can show up in a few ways:
The editor freezes and the page stops responding.
The tab reloads on its own.
You see a blank canvas after a moment.
The browser shows an error like "Aw, Snap!" or "Ooops, something bad happened!"
The whole browser closes unexpectedly.
If you're seeing any of these, work through the steps below in order.
Troubleshooting steps
1. Save a copy if you can
If the project stays open for even a few seconds, try to protect your work before troubleshooting further.
Open the project.
Right away, duplicate the project or export a quick low-res version as a backup.
Saving a copy first means that if something inside the project is causing the crash, you won't lose progress while you troubleshoot.
2. Refresh the page
Close the crashing tab.
Reopen Kittl and try the project again.
If it crashes again, do a hard refresh:
Mac: Cmd + Shift + R
Windows: Ctrl + Shift + R
A hard refresh forces the browser to reload files instead of reusing cached data.
3. Open the project in Incognito mode
Incognito mode disables cached data and most browser extensions, so it's a quick way to check whether your browser setup is the cause.
Open a new Incognito window in Chrome (Cmd + Shift + N on Mac, Ctrl + Shift + N on Windows).
Go to kittl.com and sign in.
Open your project.
If it loads without crashing here, the issue is likely caused by cached data, a browser extension, or a browser setting. Continue to step four to narrow it down.
4. Rule out extensions and your VPN
Ad blockers, script blockers, privacy tools, and VPNs or proxies can all interfere with the editor, even ones that came pre-installed or that you forgot were running.
Open your browser settings and go to Extensions.
Disable all extensions temporarily.
Turn off any VPN or proxy.
Restart your browser and open the project again.
Once the project opens without crashing, re-enable your extensions and VPN one at a time to find which one was causing the problem. If you can, also try a different network, like your home Wi-Fi versus a mobile hotspot.
5. Free up memory and close heavy apps
Low memory is a common cause of crashes, especially with large canvases, many high-resolution images, or multiple Kittl tabs open at once.
Close extra browser tabs.
Close memory-heavy apps, like video calls, streaming, or other design tools.
Restart your browser.
Reopen the project.
Where possible, avoid running Kittl alongside other demanding apps at the same time.
6. Check whether it's one project or all of them
This helps narrow down whether the issue is with a specific file or something broader.
Open a different project.
Create a new blank design.
If only one project crashes, it's likely a project-size or asset issue. If you can keep the project open long enough:
Delete or hide recently added items first, such as large images, complex groups, or effects.
Remove any unused uploads.
Save the project.
Common culprits include:
Large PNG or JPG uploads
Many objects on one page
Complex shadows or filters
Large multi-page designs
If every project crashes, it's more likely a browser, memory, or connection issue. Move on to step seven.
7. Try a different browser or device
The Kittl editor works best on an up-to-date version of Chrome. Different browsers handle graphics and memory differently, so switching can rule out a browser-specific issue.
Open the project in Chrome or Edge if you're currently on Safari or Firefox.
Try opening it on another device.
Make sure your browser and operating system are up to date.
Still crashing?
If the steps above don't fix it, reach out to the Kittl support team. To help them investigate quickly, include:
Your project link (or URL)
What happens exactly, like "opens for about 10 seconds then freezes," "tab reloads," or "blank screen"
Your operating system and browser, with version numbers
We'll take a closer look and get you back to designing as quickly as possible.
Related articles