The symbols ⇞ and ⇟ look like unusual arrows until you meet them in a keyboard diagram. There they have a practical reading: Page Up and Page Down.
They save space on keycaps and shortcut diagrams, but the arrows are only part of the story. They tell you the direction of navigation; the application decides how large the jump will be.
⇞ Means Page Up; ⇟ Means Page Down
Unicode identifies ⇞ as U+21DE UPWARDS ARROW WITH DOUBLE STROKE and annotates it as page up. ⇟ is U+21DF DOWNWARDS ARROW WITH DOUBLE STROKE and is annotated as page down.
Web keyboard specifications use the logical key values PageUp and PageDown. They also list ⇞ and ⇟ among the familiar labels for the physical keys.
So a manual that writes “press ⇞” is normally not asking you to type the arrow character. It is telling you to press the Page Up key.
What Counts as a “Page”?
On a printed document, a page has a fixed boundary. On screen, the word is looser. Page Up and Page Down generally move the viewport by roughly one visible screenful, but applications can choose a different distance or behavior.
A browser may scroll the page while keeping focus in place. A text editor may move both the viewport and the caret. A spreadsheet may jump by a block of rows. A PDF viewer may switch between fixed pages or perform continuous scrolling, depending on its view mode.
So “Page Down moves exactly one page” is too rigid as a definition. The key expresses a navigation intention; the interface supplies the mechanics.
Page Keys vs Arrow Keys
The ordinary arrow keys move in smaller steps: a character, a line, a menu item, or another unit chosen by the interface. Page Up and Page Down are designed for larger jumps through content.
| Key | Typical scale of movement |
|---|---|
| ↑ / ↓ | Small step, often one line or item |
| ⇞ / ⇟ | Larger jump, often around one viewport |
| Home / End | Jump toward a boundary such as line, document, or list start/end |
Those are common interface habits rather than fixed measurements. A spreadsheet, browser, editor, and PDF viewer can all interpret the keys a little differently.
Why Laptop Keyboards Can Hide Page Up and Page Down
On many desktop PC keyboards, PgUp and PgDn have their own keys in the navigation cluster. Smaller laptops may combine those functions with another key and a modifier such as Fn. Mac keyboards can expose page movement through shortcut combinations even when there is no large dedicated key labeled Page Up or Page Down.
In that situation, the symbol can be more useful than the physical layout. If a help screen shows ⇞, it is asking for the Page Up function; the actual key combination depends on the keyboard you have.
Shortcut notation often compresses several physical layouts into one conceptual instruction, much like Option and Alt can describe corresponding modifier positions when a Windows-style keyboard is used with a Mac.
The Unicode Characters Can Also Appear as Text
Because ⇞ and ⇟ are Unicode characters, they can be copied into a document, message, or web page. That does not make them key events. Typing or pasting U+21DE into a text field inserts the symbol ⇞ if the application accepts it; it does not normally cause Page Up navigation.
The reverse is true as well. Pressing Page Up normally triggers navigation rather than inserting U+21DE into the document.
The same is true of ⌘, ⇧, ⌫, and other keyboard symbols: they can exist as Unicode text while also serving as labels for actions that do not type those characters.
PageUp and PageDown in Web Keyboard Events
For web applications, the logical key values are PageUp and PageDown. The physical code values use the same names for dedicated keys.
The location field can matter on keyboards or keypads where the same navigation function is produced from different physical positions. That gives software a way to distinguish where an event originated when the interface needs that detail.
Most ordinary web pages should not need to reinterpret these keys. Users expect page navigation to behave consistently, and overriding established keyboard behavior can make an interface harder to use.
Page Navigation Can Preserve Context
Well-designed page navigation usually tries to move far enough to make progress without making the reader lose their place. Some viewers leave a small overlap between the old and new viewport; others keep the caret or selected row visible. That behavior is an application design choice rather than part of the Unicode meaning of ⇞ or ⇟.
For the reader, the important promise is scale: Page Up and Page Down are larger navigation steps than ordinary arrow-key movement. Exact pixels, lines, or rows are deliberately left to the interface.
Reading ⇞ and ⇟ Without Guessing
When the double-stroke arrow appears on a keycap or shortcut sheet, direction is the simplest clue: ⇞ goes up through content; ⇟ goes down. If the same character appears in ordinary prose or copied text, it may simply be the Unicode arrow itself.
A shortcut sheet and a character inspector can show the same glyph while answering different questions. One tells you what to press; the other tells you which code point is present. That distinction is more useful than trying to assign one universal behavior to the symbol itself.