Visibility/Graphics Overrides — Use visibility/graphics (VG) to control categories and overrides

Before the era of Building Information Modeling (BIM), architects and designers relied on manual layering systems in CAD software to control what appeared on each drawing sheet. In tools like AutoCAD, every element lived on a named layer, and toggling visibility meant freezing or thawing hundreds of layers by hand—a tedious, error-prone process that grew worse as projects scaled. The fundamental problem was that graphic representation was divorced from the building data itself: a wall's visual appearance on screen had no inherent connection to its material, structural role, or system classification. Revit's introduction of category-based visibility fundamentally changed this paradigm by tying graphic display to the semantic identity of each element.

The core question that Visibility/Graphics Overrides answers is deceptively simple: How do I control what appears in a specific view—and how it looks—without altering the underlying building model? This distinction between data and display is the conceptual foundation upon which every Revit documentation workflow is built. As a Visual Arts student, you will find that VG overrides function much like adjustment layers in Photoshop or display styles in Illustrator: they modify the presentation without destroying the source content.

Understanding VG overrides requires grasping the hierarchical structure through which Revit determines the final visual appearance of any element in any view. At the broadest level, Revit organizes every model and annotation element into categories—predefined groupings such as Walls, Floors, Ceilings, Furniture, and Structural Columns. These categories are further divided into subcategories (for instance, the Doors category contains subcategories for Frame/Mullion, Panel, and Opening). The VG dialog is the central command post for controlling each of these groupings, and the overrides you set in one view have absolutely no effect on any other view in the project.

The hierarchy above is the single most important concept to internalize when working with VG. When you apply an element override—say, coloring a single wall bright red—that red color will persist regardless of any filter or category setting that might otherwise apply. This is why element overrides should be used sparingly: they bypass every other layer of graphic control and can become difficult to track in large projects. In practice, most of your day-to-day VG work will happen at Level 3 (the Model Categories tab) and Level 2 (the Filters tab), where you can make broad, systematic changes that remain easy to manage and audit.

The VG Dialog: Tab by Tab

Accessing the VG dialog is straightforward: select a view and press the keyboard shortcut VV (or VG), or navigate to View → Visibility/Graphics. The dialog presents a tabbed interface, and each tab governs a different class of elements. The Model Categories tab is the workhorse: it lists every model category in the project (Walls, Doors, Windows, Furniture, Plumbing Fixtures, and so on) alongside columns for Visibility (a checkbox), Projection/Surface lines, Cut lines, and Transparency. Expanding a category reveals its subcategories, each of which can be overridden independently. The Annotation Categories tab follows the same structure but applies to 2D elements like dimensions, tags, text notes, and symbols. For Visual Arts students documenting design work, this is where you control whether room tags, door tags, or keynotes appear on a particular sheet.

Override Columns Explained

The Filters Tab — Rule-Based Overrides

The Filters tab extends VG control beyond simple category membership. A view filter is a rule that tests element parameters against specified criteria—for example, "all walls where the Fire Rating parameter equals '2-Hour.'" When a filter matches, Revit can apply graphic overrides (line color, fill pattern, visibility) to those elements alone. This is enormously powerful for Visual Arts students working on presentation drawings: you could color-code rooms by department, highlight all elements belonging to a specific design phase, or visually separate demolished versus new construction. Filters are created in the project's Filter management dialog and then assigned to individual views through the VG Filters tab. Because filters sit at Level 2 in the precedence hierarchy, they override category-level settings but yield to per-element overrides.

The second diagram reveals the internal logic of the VG dialog at a finer resolution. When you expand a category like Doors, you see subcategories such as Frame/Mullion, Opening, and Panel. Each subcategory can either inherit its graphics from the parent category (labeled "By Category") or receive its own override. This tiered approach means that you can, for example, show door panels in one color to match a design palette while leaving door frames at the default—without needing to touch individual elements. It is precisely this layered flexibility that makes Revit's VG system far more powerful than a flat layer-based approach. In a studio context, you might use subcategory overrides to de-emphasize window mullions on a presentation plan while keeping the glass fills vibrant, producing a graphic hierarchy that communicates the design intent more effectively than a drawing where every element has equal visual weight.

Imagine you are preparing a presentation-quality floor plan for an interior design studio review. The base floor plan shows every element at default graphic settings: structural columns, MEP fixtures, furniture, and annotations are all at equal visual weight. Your goal is to create a view where the furniture and finishes pop, the structure recedes, and the plan communicates a clear design narrative. Here is how you would use VG overrides step by step.

VG Overrides vs. Other Visibility Methods

Once you are comfortable with VG overrides on individual views, the natural next step is to systematize those settings through view templates. A view template is a saved configuration that can include VG category overrides, filter assignments, view scale, detail level, visual style, and numerous other view properties. When you apply a view template to a view, it enforces those settings consistently—and if you lock the template, users cannot locally override the controlled properties. This is the mechanism through which professional offices maintain graphic standards across projects with hundreds of views and dozens of team members.

Beyond view templates, advanced users leverage Dynamo scripting to programmatically generate and apply VG overrides across hundreds of views, and the Revit API to build custom tools that audit views for stray overrides or enforce graphic standards at the firm level. For Visual Arts students who go on to work in architecture or exhibition design, understanding VG overrides deeply positions you to create not only beautiful individual views but scalable graphic systems that maintain visual coherence across an entire project lifecycle.