Access Rows Hidden by Split or Freeze Panes in Excel
Question details
The user needs to access rows above the visible area of an Excel worksheet.

- Product
- Microsoft Excel
- Device & OS
- Windows
- Scenario
- A worksheet appears to stop at a particular row, preventing navigation to rows above it.
- Observed behavior
- A split window, frozen panes, or a ScrollArea restriction may be limiting access to the rows.
Open the affected workbook in Excel for Windows and select the worksheet where you cannot access the rows. Check the View tab for active Split or Freeze Panes settings.
Turn off Split and unfreeze panes
Use this solution first when the worksheet view is divided or rows remain fixed while you scroll.
On the View tab, click Split if it is enabled to remove the split window.
On the View tab, open Freeze Panes and select Unfreeze Panes if that option is available.
Scroll upward or press Ctrl+Home to check whether you can reach the top of the worksheet.

Clear the worksheet's ScrollArea restriction
Use this solution if rows remain inaccessible after removing splits and frozen panes.
Work with spreadsheets in WPS Office
WPS Office is a free, lightweight alternative with a familiar interface for working with spreadsheets. Open compatible Excel files to make migration easier, though it does not change Excel's own pane or ScrollArea settings.

Frequently Asked Questions
How do I know whether a worksheet is split?
Look for a divider separating the worksheet into independently scrollable sections. On the View tab, click Split if it is enabled to remove the divider.
Why can't I select rows above a certain point?
A worksheet's ScrollArea property may restrict the cells you can select. In Excel for Windows, press Alt+F11, select the worksheet, press F4, and clear the ScrollArea property.
What if the rows are hidden rather than blocked by panes?
Select the rows around the hidden range, then go to Home > Format > Hide & Unhide > Unhide Rows.
Why does the ScrollArea restriction come back?
Workbook VBA code may set the restriction again. Review the code in the Visual Basic Editor or ask the workbook owner whether the limit is intentional.




