The Problem (Q-score 8, ranked #104th of 303 in the Excel VBA archive)
The scenario as originally posted in 2013
So in excel I’m trying to get rid of the blank cells between my cells which have info in them by using F5 to find the blank cells, then Ctrl + – to delete them, and shift the cells up. But when I try to do that, it tells me that there are ‘No cells found’.
I’ve noticed that if I select my ‘blank’ cells, Excel still counts them:
which is weird. But if I press Delete on those selected cells, the count goes away, and then I can go F5, blanks, Ctrl + – and Shift cells up, and it works…
So my question is how can I still do that, but with these blank cells which Excel thinks aren’t blank? I’ve tried to go through and just press delete over the blank cells, but I have a lot of data and realized that it would take me WAY too long. I need to find a way to select these ‘blank’ cells within a selection of data.
Thanks in advance for your help! 🙂
Why community consensus is tight on this one
Across 303 Excel VBA entries in the archive, the accepted answer here holds solid answer (above median) status — meaning voters are unusually aligned on the right fix.
The Verified Solution — solid answer (above median) (+13)
Verbal answer — walkthrough without a code block
Note: the verified answer is a prose walkthrough. If you need a runnable sample, check Excel VBA entries ranked in the top 10 of the same archive.
a simple way to select and clear these blank cells to make them blank:
- Press ctrl + a or pre-select your range
- Press ctrl + f
- Leave find what empty and select match entire cell contents.
- Hit find all
- Press ctrl + a to select all the empty cells found
- Close the find dialog
- Press backspace or delete
When to Use It — classic (2013–2016)
Ranked #104th in its category — specialized fit
This pattern sits in the 96% 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 2013 and 2026
The answer is 13 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.