Can't export board as a JPG

@Abi Williams - I'm replying from my phone, so I'll be keeping this fairly short.

First, exactly how are you exporting? There are two ways:

1. Using the board export by the board title and

2. Exporting a frame

Is you are using option one, are your wireframe elements in a frame? And if they aren't, have you tried putting them into a frame and exporting the frame as an image?

Any screenshots you can provide will help us better understand exactly what and how you are trying to export and what you are seeing.

Thanks - trying to export frame by frame - screenshots attached….

@Abi Williams - I can't view the Google Drive file as the permissions aren't set to allow it.

You can add images to your reply using this button:

@Olga Tsyba - What type of plan are you on?

How are you trying to export - board or frame?

Can you provide screenshots or a screen recording, e.g., Loom?

I am on a Consultant Plan and am also a member of a Team Plan and can export both the board and frames as images from both plans:

When I select Image it only show Vector active. Doesn’t matter frame or board. I am on a paid plan, and I used to be able to export  images two weeks ago. Then something happened.

@Olga Tsyba - As Kiron mentioned, perhaps the Board Content Settings may have something to do with it, however, when I set them so that only the board owner can copy board content and I open the board as a regular team member and the board owner, the “export this board” option is completely missing.

Reset application data

From your screenshot, it looks like you are using a Miro desktop app. I would suggest that you try the Reset application data option - instructions are here:

https://help.miro.com/hc/en-us/articles/360017572854-Desktop-App#h_01EVGAY54JY5E9S7J62FRCX6D4

Miro in a browser

One more question: Does this also happen for the same board when you try to export as JPG from a browser?

@Abi Williams - The browser is not supposed to make as difference as all modern browser makers would surely strive to follow standards (as would Miro). However, bugs make their way in from time to time - or perhaps not even bugs, but one browser’s development teams interpretation of a how a standard should be implemented can be slightly different than the others. So, yes, the browser make/version can definitely have something to do with it.

Is it not working in Safari but does in Chrome? If so, we should definitely report this to Miro support.

@Olga Tsyba - I would suggest that you report this to Miro Support. It would be helpful if you could update this post with what Miro support tells you.