Photo by Marvin Meyer

As many of you already know, opening a 360 product view from your hard-drive may not always work "out-of-the-box" in modern web browsers. Since the release of Firefox 68 and the announcement that the next version of Microsoft Edge is based on the Chromium browser, pretty much everybody who uses WebRotate 360 need to be aware of the required extra steps to configure your browser for local tests or offline viewing.

The good news is that everything works without issues once the 360 spins are uploaded online or loaded via a local web server on your computer or network. Also, the next version of WebRotate 360 Product Viewer will come with a built-in web browser that will be pre-configured for pain-free local and offline viewing.

Update [Jun 25, 2021]: Latest v3.6.5 beta now includes a built-in web server, so as along as you lunch the browser previews from inside SpotEditor (i.e not manually by clicking published html files), the following steps are now NOT required in v3.6.5 beta and onward.

Now lets see how to configure browser security for your local testing in these popular web browsers:


When you launch a local preview upon publish in SpotEditor, it already passes all required configuration to Chrome (Opera, Edge) such that all should just work. There's one important caveat: you have to make sure that there are no running Chrome windows that you have launched manually, i.e that were not launched automatically by SpotEditor. As otherwise the settings that we pass to Chrome are ignored.

So simply close any running Chrome windows once before starting to use SpotEditor and it will then work every time you publish and launch a local Chrome preview in SpotEditor. On Mac, right-mouse click the Chrome icon in Dock and select Quit.

If you want to launch a published view manually by double-clicking the html file or dragging it to a Chrome window, things get trickier as you have to first configure Chrome to allow loading local files.

On Windows we recommend creating an extra shortcut for Chrome (on your desktop for example) and pasting this extra option at the end of the Target field of the shortcut:  --allow-file-access-from-files. You may also rename the shortcut so you don't use it accidentally for regular web browsing:

On Mac, we need to use Terminal app and an extra script file to launch Chrome with required permissions as follows:

  • Create an empty text file and paste this line:
    open /Applications/Google\ --args --allow-file-access-from-files
  • Save the file as to your desktop for example
  • Launch Terminal app and type in the following (replace YourUserName):
    chmod +x /Users/YourUserName/Desktop/
  • Close Terminal app.

Now that you have prepared an executable script, you can launch Chrome with required settings whenever you need to test your 360 product views by opening the script file in Terminal via the "Open With" command in Finder.

Same instructions apply to Opera and the latest versions of Microsoft Edge browser.

Consider installing Firefox just for testing your published 360 product views as configuring offline file access in Firefox is pretty straightforward as described below.


Follow these steps in Firefox to enable the loading of local files the way it has been possible in the last ten or so years until the release of Firefox 68.

  • Open Firefox.
  • In the address bar type in about:config
  • You will see a message, warning that changing anything there may be harmful.
  • Confirm that you accept the risk to proceed.
  • A new page now opens where you can change Firefox configuration.
  • In the search bar at the top of this page type in privacy.
  • Find this option in the filtered list privacy.file_unique_origin
  • Click it until it displays as false as per attached screenshot.

This does expose you to a known security issue if somebody tricks you into downloading and launching a rogue html file from your hard-drive so you may consider setting up a separate Firefox profile if this is a concern.


To be able to preview your published work locally in Safari 11 (and up), navigate to Safari's Develop menu and check "Disable Local File Restrictions" as shown below. If you don't see the Develop menu in the menu bar, choose Safari > Preferences, click Advanced, then select "Show Develop menu in menu bar".