Hi ​@Erinpollock, thanks for sharing what happened.

To help us investigate further, could you let us know a bit more about what you noticed? For example:

• Did this happen right after a specific action (e.g., applying a template, converting shapes, or duplicating the board)?

• Are you seeing the same issue if you refresh the board or try in a different browser/device?

• Do you recall if this board was created from a template or built from scratch?

In the meantime, one thing you might try is checking the board version history to see if there’s a version from before the issue occurred that you can restore.

We’ll keep an eye on this thread — the more detail you can share, the quicker we can pinpoint what’s going on.

Hello Miro Support,

I am writing to report a critical issue with a large, 250-page board. Upon returning to my computer, I discovered that all the shapes and lines in the entire document have been significantly shifted and misaligned. The text, however, remains in its correct position.

This occurred without any user interaction or edits on my part. I was away from the computer and not actively working on the file when this happened.

Key Details:

• Software: Miro (both desktop app and web version)

• Board Size: Approximately 250 "pages" (frames or sections).

• Elements Affected: Shapes and connection lines are all shifted and in the wrong position.

• Elements Unaffected: All text elements are correctly positioned.

• Troubleshooting Steps Taken:

  • Restarted the Miro desktop application.

  • Attempted to view and work on the board using the web version.

  • The issue persists across both platforms, suggesting the problem is with the file itself.

This bug has rendered my entire project unusable. I understand from the Miro community that similar issues with shifting elements have been reported, and I believe this may be a manifestation of that same underlying problem.

Could you please provide guidance on how I can recover my board to a previous, correct state? I am also willing to provide History or any other information you need to help investigate this critical bug.

Thank you,