Hiding an Excel worksheet with VBA

calendar_today Asked May 12, 2009
thumb_up 33 upvotes
history Updated April 14, 2026

Direct Answer

To hide from the UI, use Format > Sheet > Hide To hide programatically, use the Visible property of the Worksheet object. If you do it programatically, you can set the sheet…. This is a 3-line Excel VBA snippet, ranked #19th of 303 by community upvote score, from 2009.


The Problem (Q-score 19, ranked #19th of 303 in the Excel VBA archive)

The scenario as originally posted in 2009

I have an Excel spreadsheet with three sheets. One of the sheets contains formulas for one of the other sheets.

Is there is a way of hiding it that sheet pprogrammatically, which contains these formulas?

Why this Range / Worksheet targeting trips people up

The question centers on reaching a specific cell, range, or workbook object. In Excel VBA, this is the #1 source of failures after activation events: every property (.Value, .Formula, .Address) behaves differently depending on whether the parent Workbook is explicit or implicit.


The Verified Solution — elite answer (top 10 %%) (+33)

3-line Excel VBA pattern (copy-ready)

To hide from the UI, use Format > Sheet > Hide

To hide programatically, use the Visible property of the Worksheet object. If you do it programatically, you can set the sheet as “very hidden”, which means it cannot be unhidden through the UI.

ActiveWorkbook.Sheets("Name").Visible = xlSheetVeryHidden 
' or xlSheetHidden or xlSheetVisible

You can also set the Visible property through the properties pane for the worksheet in the VBA IDE (ALT+F11).


When to Use It — vintage (14+ years old, pre-2013)

Ranked #19th in its category — specialized fit

This pattern sits in the 90% tail relative to the top answer. Reach for it when your scenario closely matches the question title; otherwise browse the Excel VBA archive for a higher-consensus alternative.

What changed between 2009 and 2026

The answer is 17 years old. The Excel VBA object model has been stable across Office 2013, 2016, 2019, 2021, 365, and 2024/2026 LTSC, so the pattern still compiles. Changes that might affect you: 64-bit API declarations (use PtrSafe), blocked macros in downloaded files (Mark-of-the-Web), and the shift toward Office Scripts for web-first workflows.

help
Frequently Asked Questions

Why is this answer the top decile of Excel VBA Q&A?
expand_more

Answer score +33 vs the Excel VBA archive median ~11; this entry is elite. The score plus 19 supporting upvotes on the question itself (+19) means the asker and 32 subsequent voters all validated the approach.

Does the 3-line snippet run as-is in Office 2026?
expand_more

Yes. The 3-line pattern compiles on Office 365, Office 2024, and Office LTSC 2026. Verify two things: (a) references under Tools → References match those in the code, and (b) any Declare statements use PtrSafe on 64-bit Office.

This answer is 17 years old. Is it still relevant in 2026?
expand_more

Published 2009, which is 17 year(s) before today’s Office 2026 build. The Excel VBA object model has had no breaking changes in that window. Three things to re-test: (1) blocked macros on downloaded files (Mark-of-the-Web), (2) 64-bit API declarations (PtrSafe, LongPtr), (3) any shift toward Office Scripts for web scenarios.

Which Excel VBA pattern ranks just above this one at #18?
expand_more

The pattern one rank above is “Create Excel file in Java”. If your use case overlaps, compare both before committing.

Data source: Community-verified Q&A snapshot. Q-score 19, Answer-score 33, original post 2009, ranked #19th of 303 in the Excel VBA archive. Last regenerated April 14, 2026.

excel-vba