Now Reading
How to close your viewports in Blender 2.8?
1

How to close your viewports in Blender 2.8?

by Design SyncJanuary 22, 2019

You have accidentally opened too many viewports in Blender and now you don’t know how to close them. Follow the simple step by step guide below to clean all those split windows.

1. Move your mouse cursor inbetween the divided viewports.

2. Right Mouse click and select join from the Area Option popup menu.

3. Move your cursor over to the viewport you would like to collapse.
A large arrow icon appears indications the region you wish to collapse the viewport.

4. Repeat this step for any other viewports you wish to close.

Version: Blender 2.8 Beta (January 2019)
Type of application: 3D Software
Related Sections: General

Blender is an open source software for 3D creation. It offers modeling, texturing, rigging, animation, simulation, rendering, compositing and video editing used for animation, film, video games and more. The latest Blender edition, 2.8 is undergoing major development and is showing vast improvements from the previous 2.79 version. Click here to download the latest Blender 2.8 update.

1 Comments
  • Darryl Blake
    March 3, 2021 at 7:05 pm

    I have the latest version of Blender – 2.92. I’m a begginner and was following along with a tutorial. Where they were saying how to open a extra viewport.
    I create 2 extra viewports. By right click the edge – vertical – and dragged two new windows.
    he then showed how you can create more by hovering over the top left corner and drag right to create more windows. And do the same only left to close them.
    I went to close all the new windows. But when I got to the original two, when I dragged left. I got a (Ghostbuters – circle with a line) I tried to right click the edge and choose join. But the only options were to swap.

    I opened up a new file, create some windows and was able to close all those just fine. But this one file where all my work is, I cannot close.

    I Looked in the official Blender forums and found a bug from 2012 with the exact same problem. The problem wasn’t solved he just reinstalled windows. I’d rather not do that.

    Any ideas?

Leave a Response