Full page in one click
Click the Hip FullPage icon to start a full-page capture immediately.
FULL PAGEHIP FULLPAGE / HELP
캡처에서 결과물까지.
Every step, right here.
A clear guide to using Hip FullPage, from your first capture to editing, the local Library and export.
START CAPTURING
Three ways in.
The same product flow.
Use the extension icon for a full-page capture. For more focused captures, use the context menu or keyboard shortcuts.
Quick access to other modes
Open Visible Area, Selected Area, Element Capture and Library directly from the page.
4 SHORTCUTSSpeed up the workflow
Assign your own Chrome shortcuts to the capture modes you use most.
CUSTOMIZE01 / GETTING STARTED
Four steps.
One flow.
Hip FullPage follows one simple flow: capture, review, refine if needed, then export.
01
Start a capture
Click the Hip FullPage icon in your browser toolbar. Full-page capture starts in one click; the other capture modes are available from the menu.
02
Review the result
When capture finishes, Preview opens automatically. Check the result, recapture, copy, print or export it directly.
03
Edit and prepare
Use crop, box, arrow, text and blur tools to prepare the screenshot for sharing.
04
Keep it local
Your captures stay in the Library in this browser. Reopen, edit or export them later.
02 / CAPTURE MODES
Capture only
what you need.
Full Page is the core workflow. Visible Area, Selected Area and Element Capture are there for faster, more focused jobs.
Full Page
Automatically scrolls and captures the page from top to bottom.
Visible Area
Captures exactly what is visible in the viewport.
Selected Area
Captures only the region you select.
Element
Targets one interface or content element.
03 / EDIT & EXPORT
Make the capture
ready to use.
01Crop and refine the frame.
02Mark important areas with boxes, arrows and text.
03Blur sensitive areas.
04Export as PNG, JPEG, WebP or PDF.
OUTPUT
When the work is done,
choose the right output.
Preview keeps copy, download, PDF and print in one place. You can also set JPEG and WebP quality from Settings.
Put the capture on your clipboard and paste it into another app.
Choose the right format for UI, photos or a smaller file size.
Export as one continuous page or printable A4 sheets.
Move from Preview straight into the browser print flow.
04 / LOCAL LIBRARY
캡처를
stay with you.
In the current Free release, captures are stored locally in your browser. No account is required, and screenshots are not automatically uploaded to a remote server.
Privacy details
05 / SETTINGS
Tune it
to your workflow.
Manage capture speed, automatic Preview, file naming, export preferences, PDF options, Library behavior and shortcuts in one place.
Pace and automatic Preview.
Templates with domain, date, time and mode.
Format, quality and download behavior.
Continuous page or A4 layout.
Local storage and automatic cleanup.
Manage Chrome keyboard assignments.
No account, no cloud upload.
Choose the Hip FullPage interface language.
PRIVACY
Local by default.
No account requiredNo cloud syncNo automatic screenshot upload
Read the privacy policy 06 / TROUBLESHOOTING
If something looks off,
start here.
Parts of the page are missing or blank.
Wait for the page to finish loading, allow animated content to settle, then capture again. If needed, try a slower capture speed in Settings.
A sticky header or sidebar repeats.
This can happen on dynamic pages with nested scrolling. Make sure you are using the latest version; if it continues, include the page address in an issue report.
Capture does not start.
Chrome internal pages and some restricted browser URLs may block extension access for security reasons. Try again on a normal webpage.
Captures disappeared from the Library.
The Library depends on local browser data. Clearing browser data, removing a profile or changing devices can remove local captures.
Why is the context-menu language different?
Chrome-managed extension menu labels follow the browser language. The manual language setting inside Hip FullPage changes the product screens.
Why do very long pages take longer?
Long, dense pages require more segments, images and local assembly. On lazy-loaded pages, a slower capture pace can produce a more reliable result.
Still not solved?
Send us the issue. A screenshot is included only if you explicitly attach one.