MURAL is a HTML5 web application and works best with Chrome, but we also support Firefox, IE11 and Safari. We also have native apps for Windows10, iOS (see app store) and the Microsoft Surface Hub.

Wondering what browser and software versions you need to collaborate most efficiently in MURAL? Here's a list of supported browsers and versions when using MURAL on the web:

Supported Browsers

  • Chrome: 51 or above
  • Edge: 43 or above
  • Safari: 9 or above
  • Firefox: 46 or above
  • Internet Explorer: 11

A note on Internet Explorer 11

MURAL's performance and responsiveness in Internet Explorer 11 is not as good as with other modern browsers. Consider that Internet Explorer 11 was launched in October 2013.

Also, due to a technical limitation in Internet Explorer 11, you may not be able to zoom in or out on certain Microsoft trackpads. As a workaround, you can try any of these alternatives:

  • Use CTRL + to zoom in and CTRL -  to zoom out
  • Use the + and - controls over the Mini Map (bottom right)
  • Connect a mouse and use the scroll wheel

Mobile Devices

  • iPhone: 6S or above
  • iPad: iPad (5th gen.) and iPad Pros. iPad Mini is not supported if you want to use MURAL Scan.
  • Operating system: iOS 11 or above

Touch Screen Devices 

MURAL will work on any touch screen device that runs Windows 10, has more than 16gb RAM and the latest touch screen technology. MURAL has direct integrations with the Microsoft Surface Hub and Surface Hub Pro.

In the event that you choose to go with a non-Windows device , or touch screens without an internal pc (called a nuke), you can connect a Windows 10 laptop to these screens using a HDMI and USB cable and run MURAL from there.

Having connection issues?

Try restarting your computer, a different browser (i.e. Chrome, Firefox), or if you get a constant reconnecting message, check this link to see if websockets are enabled.

If your websockets are not enabled, please reach out to your IT team. They can follow these instructions to allow your team to use MURAL:

1) Allow websockets and secure web sockets (on

2) Don't manipulate headers or user agent internally on IDS/IPS

3) Don't filter protocol update answers 

Now, you can collaborate as efficiently as ever!

Did this answer your question?