When in non-full-screen mode, Safari lets me use the ⌘+| shortcut or View > Hide Toolbar to hide the URL and search bar, etc. However, when I'm in Full Screen mode, this option is greyed out. Is there any way I can hide it without exiting Full Screen?
Asked
Active
Viewed 1.7e+01k times
3 Answers
46
In Safari 10.0.1 on macOS Sierra it is quite simple - you have to uncheck View > Always Show Toolbar in Full Screen to hide the toolbar.
Mateusz Piotrowski
- 2,014
-
3This should be the top-voted answer. – Sridhar Ratnakumar Sep 30 '17 at 19:04
-
2Note that you might have to go into Full Screen mode before you can uncheck it – nachocab Apr 06 '19 at 08:43
-
1I feel like an idiot that I had to Google this and didn't just find it in the menus. – stef Feb 18 '21 at 02:56
10
Enter full screen mode, right-click anywhere around the address bar then click "Hide Toolbar" in the menu that appears.

Although next time you enter full screen mode the toolbar comes back.
binarybob
- 9,875
-
3Be careful, because once you do this, the only way to get the bar back is to exit and then enter full screen mode again. – Sam Spencer Apr 19 '12 at 22:24
-
1
-
8
-
9
Open console (⌥⌘C or Develop > Show Error Console), paste this code:
(function() {
var el = document.createElement('div'),
docEl = document.documentElement;
el.innerText = 'Go to fullscreen view';
el.setAttribute('style', 'position: fixed; top: 10%; left: 10%; padding: 30%; background: #000; color: #fff; opacity: .7; cursor: pointer;')
document.body.appendChild(el)
el.onclick = function() {
if (docEl.requestFullscreen) {
docEl.requestFullscreen();
} else if (docEl.mozRequestFullScreen) {
docEl.mozRequestFullScreen();
} else if (docEl.webkitRequestFullscreen) {
docEl.webkitRequestFullscreen();
}
document.body.removeChild(el);
};
})();
and click the black box.
You need to activate Developer-Tools for this solution. To enable Developer-Tools, go to Advanced, click "Show Develop menu in menu bar" at the bottom of the window.
rgtk
- 255
-
-
-
@ralfix, your solution won't work since Webkit-based browser require function like this triggered by user action (via click event for example). – rgtk Jul 20 '15 at 10:11
-
