Report a bug so it can be fixed
Where to report a bug from anywhere in Voidcanvas, what to write so it gets fixed quickly, and exactly what the report sends.
Beginner3 min readUpdated 25 September 2026Help
On this page
A good bug report lets someone else make the problem happen on their own screen. Once they can see it, they can fix it. This page shows what to write and where to send it.
Where to report it
- In the Editor: Help, Report a bug…. On a phone, tap the question mark at the top of the Editor.
- In Studio, Effects and the quick tools: the question mark next to the module switch, then Report a bug.
- Anywhere else: the Report a bug page, linked in the footer of every page.
Inside the app the report opens in a box over your work, so nothing is closed or lost while you write it.
For ideas and general comments, Help, Send feedback… is quicker.
Before you report
- Try it again. If it happens every time, note the exact steps. If it happens only sometimes, say so.
- Reload the page and try once more. That rules out a one-off glitch.
- Check Troubleshooting. Some messages, such as storage being full, have a quick fix.
What to write
Three things make a report useful: what you did, what you expected, and what happened instead.
| Part | Weak | Useful |
|---|---|---|
| What you did | I was editing text. | Opened a PSD, double-clicked the headline text layer, changed the font to Bebas Neue. |
| What you expected | It to work. | The headline to show in Bebas Neue. |
| What happened | It broke. | The text disappeared from the canvas but is still listed in the Layers panel. |
- Number the steps, starting from something anyone can do, such as ‘Pick Instagram post on the start screen’.
- Copy any message word for word. Messages such as Export failed. Try a smaller size. point straight at the cause.
- Give sizes. The design size, the size of the photo you added, the export scale. Many problems only appear with large files.
- Say whether it used to work. ‘This worked last week’ narrows the search a lot.
- One problem per report. Two bugs in one report often means one gets missed.
The form, field by field
| Field | What to put |
|---|---|
| What went wrong? | One line. The only required field. |
| Where? | The part of Voidcanvas. It is filled in from the page you came from; change it if that is wrong. |
| How can we make it happen? | Your numbered steps. The most useful part of any report. |
| What did you expect instead? | What you thought would happen. |
| How much does it get in the way? | Stops my work, Gets in the way or Looks wrong. |
| Does it happen every time? | Every time, Sometimes or Only once. |
| Optional. Only if you want a reply. |
What is attached, and what is not
Include technical details is ticked by default. Untick it and only what you typed is sent. With it on, the report also carries:
- The page you were on, device type (desktop, tablet or phone), browser, operating system, screen and window size, language, time zone, and whether Voidcanvas is installed as an app.
- The ids of the last few commands you used, such as
layer.duplicate. Never their content. - Up to five recent error messages from this tab, with any web addresses removed.
Press See exactly what is sent to read every value before you send. Your images, file names, text and layers are never included. Bug reports are sent even when anonymous usage counts are off, because you chose to send one. See Privacy and data.
After you send it
Your work stays safe on your device while you wait for a fix. If a problem is blocking you, export what you have and keep a .void copy. See Saving and your files.