🧙 How to Jump to the Top or Bottom of Any App on macOS
I spend a lot of my day at the bottom of something. A long Slack channel, a 400-comment GitHub thread, a chat log, a diff that someone clearly generated with a for-loop. And constantly I want to get back to the top — or shoot down to the very bottom — and on a Mac there is no obvious, universal way to do it.
You’d think there would be. iOS has it: tap the status bar, you’re at the top. Every iPhone user knows that one. On the Mac? It depends entirely on which app you happen to be in, and the answer changes app to app in ways that have quietly annoyed me for years.
So here’s the actual state of jumping to the top or bottom on macOS — the shortcuts that exist, why they’re such a mess, and what I eventually did about it.
The keyboard shortcuts (such as they are)
In a lot of apps, ⌘↑ (Command + Up Arrow) jumps to the top of the document and ⌘↓ to the bottom. Safari, Chrome, Notes, most plain text views — this works. Great.
Except:
- In Finder, ⌘↑ doesn’t scroll to the top. It opens the enclosing folder. Muscle memory from your browser will quietly send you up a directory.
- In Terminal and iTerm, ⌘↑ scrolls to the previous command, not the top. To reach the very top of the scrollback you want ⌘Home — if your keyboard even has a Home key.
- Which is the other problem: Home and End. On a full-size keyboard, Home jumps to the top of a field and End to the bottom, and they’re great. But Apple stopped putting Home and End keys on laptops a long time ago. On a MacBook you fake them with Fn + Left Arrow (Home) and Fn + Right Arrow (End) — and even then, in many apps they move the text cursor rather than the scroll position, which is a different thing entirely.
There’s also Space to page down and Shift + Space to page up, which is genuinely useful and underused — but that’s paging, not jumping, and you’ll be mashing it a while to clear a long page.
So the honest summary: there are roughly four different ways to scroll to the top of something on a Mac, none of them work everywhere, and the keys you’d most want to reach for don’t exist on the keyboard you actually own.
Why is it like this?
I don’t think anyone decided this on purpose. macOS never standardized “go to top / go to bottom” the way it standardized copy and paste — each app’s developer wired up ⌘↑, Home, and the rest to whatever made sense in their app, and they all made slightly different, individually reasonable choices. Then laptops dropped the dedicated navigation keys to save space, and the whole thing calcified into the mess we have now. iOS, built later and from a blank page, got the clean version: tap the top, you’re home.
You adapt, of course. You learn that Finder is weird, you learn ⌘Home in the terminal, you reach for the scrollbar when in doubt. But “you adapt” is the sentence I tend to say right before I build something.
What I did about it
I made a tiny menu-bar app called Scroll Elevator. The idea is almost embarrassing in how direct it is: when you scroll, two little elevator buttons appear right at your cursor — one to jump to the top, one to the bottom. Click and the window leaps there. Hold one and the page glides, faster the longer you hold. Move your mouse away and they fade.
What makes it click is that your hand never leaves the trackpad. To hit Home or ⌘↑ you reach for the keyboard and have to remember which incantation this particular app wants; Scroll Elevator puts top and bottom under the cursor your hand is already on. And it behaves the same in Chrome, Finder, Preview, Mail, Xcode, and your terminal — because under the hood it drives each app’s own scrollbar instead of firing a keystroke and hoping.
It’s $4.99, one time, signed and notarized, and nothing ever leaves your Mac. If you’d rather not pay, the whole thing is open source and you can build it yourself for free — I mean that, the instructions are right there in the README.
Is a dedicated app for “scroll to the top” overkill? Maybe. But I do it something like fifty times a day, and the friction was real enough that I’d rather have one button than a flowchart of keyboard shortcuts in my head. If you’ve ever pressed ⌘↑ in Finder and watched it jump up a folder instead, you know the exact feeling I’m talking about.
I spend a lot of my day at the bottom of something. A long Slack channel, a 400-comment GitHub thread, a chat log, a diff that someone clearly generated with a for-loop. And constantly I want to get back to the top — or shoot down to the very bottom — and on a Mac there is no obvious, universal way to do it.
You'd think there would be. iOS has it: tap the status bar, you're at the top. Every iPhone user knows that one. On the Mac? It depends entirely on which app you happen to be in, and the answer changes app to app in ways that have quietly annoyed me for years.
So here's the actual state of jumping to the top or bottom on macOS — the shortcuts that exist, why they're such a mess, and what I eventually did about it.
## The keyboard shortcuts (such as they are)
In a lot of apps, **⌘↑ (Command + Up Arrow)** jumps to the top of the document and **⌘↓** to the bottom. Safari, Chrome, Notes, most plain text views — this works. Great.
Except:
- In **Finder**, ⌘↑ doesn't scroll to the top. It opens the *enclosing folder*. Muscle memory from your browser will quietly send you up a directory.
- In **Terminal and iTerm**, ⌘↑ scrolls to the previous command, not the top. To reach the very top of the scrollback you want **⌘Home** — if your keyboard even has a Home key.
- Which is the other problem: **Home and End**. On a full-size keyboard, Home jumps to the top of a field and End to the bottom, and they're great. But Apple stopped putting Home and End keys on laptops a long time ago. On a MacBook you fake them with **Fn + Left Arrow** (Home) and **Fn + Right Arrow** (End) — and even then, in many apps they move the *text cursor* rather than the *scroll position*, which is a different thing entirely.
There's also **Space** to page down and **Shift + Space** to page up, which is genuinely useful and underused — but that's paging, not jumping, and you'll be mashing it a while to clear a long page.
So the honest summary: there are roughly four different ways to scroll to the top of something on a Mac, none of them work everywhere, and the keys you'd most want to reach for don't exist on the keyboard you actually own.
## Why is it like this?
I don't think anyone decided this on purpose. macOS never standardized "go to top / go to bottom" the way it standardized copy and paste — each app's developer wired up ⌘↑, Home, and the rest to whatever made sense in their app, and they all made slightly different, individually reasonable choices. Then laptops dropped the dedicated navigation keys to save space, and the whole thing calcified into the mess we have now. iOS, built later and from a blank page, got the clean version: tap the top, you're home.
You adapt, of course. You learn that Finder is weird, you learn ⌘Home in the terminal, you reach for the scrollbar when in doubt. But "you adapt" is the sentence I tend to say right before I build something.
## What I did about it
I made a tiny menu-bar app called **[Scroll Elevator](https://kevintang.xyz/apps/scroll-elevator/)**. The idea is almost embarrassing in how direct it is: when you scroll, two little elevator buttons appear right at your cursor — one to jump to the top, one to the bottom. Click and the window leaps there. Hold one and the page glides, faster the longer you hold. Move your mouse away and they fade.
What makes it click is that your hand never leaves the trackpad. To hit Home or ⌘↑ you reach for the keyboard and have to remember which incantation *this particular app* wants; Scroll Elevator puts top and bottom under the cursor your hand is already on. And it behaves the same in Chrome, Finder, Preview, Mail, Xcode, and your terminal — because under the hood it drives each app's own scrollbar instead of firing a keystroke and hoping.
It's $4.99, one time, signed and notarized, and nothing ever leaves your Mac. If you'd rather not pay, the whole thing is [open source](https://github.com/NSEvent/scroll-elevator) and you can build it yourself for free — I mean that, the instructions are right there in the README.
Is a dedicated app for "scroll to the top" overkill? Maybe. But I do it something like fifty times a day, and the friction was real enough that I'd rather have one button than a flowchart of keyboard shortcuts in my head. If you've ever pressed ⌘↑ in Finder and watched it jump up a folder instead, you know the exact feeling I'm talking about.