Documentation
Troubleshooting
Most problems in Graphite4D come from the browser's graphics support, a lost connection or the same project open in two places. Your stored work is kept through all of them. Start with the section that matches what you see.
Browsers and graphics
Graphite draws the 3D view with WebGPU. Use a browser that supports it, such as a current version of Chrome. Safari supports WebGPU on macOS Tahoe 26 or later. On an older macOS, updating Safari alone doesn't enable it, so use Chrome or the compatibility renderer instead.
A label in a corner of the 3D view names the renderer, followed by Details or Why?. Select it to see live performance and renderer diagnostics.
| Label | What to do |
|---|---|
| WebGPU | Nothing. This is the normal renderer. |
| WebGL2 · compatibility renderer | Nothing. Graphite is using compatibility mode, which works without WebGPU. |
| WebGPU unavailable | The browser didn't provide WebGPU. Follow the guidance in the panel, or choose Use WebGL2 compatibility. |
| WebGPU · device lost, WebGPU · rendering failed or Renderer unavailable | Choose Retry WebGPU. If it fails again, choose Copy report and contact support. |
If WebGPU is unavailable:
- Check that graphics or hardware acceleration is turned on in your browser's settings, then quit and restart the browser completely.
- In Chrome, open
chrome://gputo see its WebGPU status and any problems it detected. - If WebGPU still isn't available, choose Use WebGL2 compatibility.
Graphite remembers the compatibility choice in this browser, but still tries WebGPU first each time. Retry WebGPU clears the choice and rebuilds the view. Retrying never changes your project.
Large models and performance
Select the renderer label to open Live performance. It shows the framerate, draw calls, rendered triangles and Graph evaluation details. A still view resting at 0 fps is normal; Graphite only draws when something changes.
When you change a large model, Graphite recomputes exact geometry, and the status bar shows Updating exact geometry…. On very large models this can take several seconds.
- Build repeated parts with recipes, Array, Distribute or Repeat floors. Graphite reuses results for parts that haven't changed. See Recipes and the graph.
- Use Procedural perforation for perforated panels instead of modeling each hole. It adds no geometry.
- Press I to isolate the selection, and Shift I to hide the rest of the model while you work inside a recipe or isolated selection.
- In Site & Context, choose Diagram or Off when you don't need Photo. Photo streams detailed 3D surroundings.
Some limits keep models responsive:
| Item | Limit |
|---|---|
| Project data, for cloud saving and project files | 4 MB |
| Array | 2,000 elements in total |
| Repeat once for each item | 500 items |
| Merge collections | 16 inputs, 2,000 items |
| Texture image | 256 KiB each |
"Project recovery needs attention"
This status means the project couldn't finish opening. Your stored work is preserved, and Graphite doesn't create a replacement project.
- Read the message in the message bar near the bottom of the 3D view.
- Choose its button, usually Retry opening.
- If the message says the project is not available, check that you're signed in to the right account and in the right workspace. Copies on a device belong to the account that made them.
- If the project service is slow, Graphite can open the copy saved on this device, and the message says so. Keep working on it, or choose Retry opening.
If you see "This project changed in another browser session", the same project is open in another tab or window. Close the other one, then choose Reload saved project. Keep one tab per project to avoid this.
Conflicts
Conflict · 2 local edits in the top bar means your edits overlap changes someone else saved. Your edits stay on this device. Open the collaboration panel and choose Use cloud version, Apply non-conflicting edits or Keep as a separate project. See When edits conflict.
If Properties instead shows "Cloud changes need review before saving can continue", choose Keep local work as a new project. Graphite saves your version as a separate project whose name ends in "recovered copy".
Working offline
If your connection drops while Graphite is open, keep working. The top bar shows Offline and the number of pending edits. Graphite saves each edit on this device and sends them when you reconnect. You don't need to do anything.
You can't open Graphite while offline. The page shows "You're offline"; reconnect and choose Try again. Projects saved on the device are still there.
Graphite keeps your device copy in browser storage. Private and incognito windows erase that storage when they close, and blocking site data can prevent it; you may then see "IndexedDB is unavailable. Device changes cannot be saved in this browser." Use a normal window and allow site data for Graphite.
Clear a stuck state safely
Work through these in order, and stop when the problem clears:
- Save a file first. Open the project menu and choose Save file (⌘ S on a Mac, Ctrl S on Windows).
- Choose the button in the message bar, such as Retry, Retry opening or Reload saved project.
- Close other tabs that have the same project open.
- Reload the page. Pending edits on this device survive a reload.
- Reopen the project from your projects list, or bring back your saved file with Open project file.
To reset only the toolbar, open All tools, expand Toolbar preferences and choose Reset pins and learned tools.
Get help
Use Help → Contact support in the app. Tell us what you were doing, the exact save status or message you saw, and your browser and operating system. For display problems, select the renderer label, choose Copy report and paste it in. The report lists your browser and the renderer's steps; it contains no project geometry. Never send your password or API keys.