A full-page screenshot is assembled from several visible views of a webpage. The lightingshot extension scrolls the page, captures those views, and opens their combined image in its editor. That works best with a finite page whose content and layout stay still. Changing feeds, nested scrolling panels, and unusually large pages need more care.
Start with the symptom below. You do not need the extension to edit an image you already have: you can open the web image editor and import a local screenshot instead.
Start with a reliable capture setup
- Check installation. This release is a manually installed development extension for compatible Chromium browsers. Download the ZIP from the homepage, unzip it, and use Load unpacked in the browser's extension management page. The installation instructions show the Chrome and Edge steps.
- Open an ordinary webpage. Use a normal HTTP or HTTPS page. This lightingshot release rejects browser settings pages and extension store pages. Do not assume an image editor can bypass a protected viewer's access restrictions.
- Prepare the content. Dismiss overlays that you do not want in the image. Wait for the relevant images and sections to appear. If you scroll to encourage lazy-loaded content to appear, return to a stable starting view before capturing.
- Choose the capture mode. Select 截取整个页面 (Capture entire page) for scrolling capture or 截取可视区域 (Capture visible area) for just the current viewport.
- Keep the target tab active. Do not switch tabs, navigate, resize the window, or interact with the page while the capture is running. Wait for the editor to open, then inspect the result before exporting it.
The capture stops when I switch tabs
lightingshot checks that the target remains the active tab before and after capture steps. Switching away can intentionally stop the operation. Chrome's captureVisibleTab API captures the visible area of the active tab in a window; keeping that tab selected is part of this extension's capture workflow.
Return to the target page and start again. If you are comparing several pages, capture and export them one at a time. The error editor may show the sample image beside an error status; that sample is not a successful capture of your webpage.
The image is missing content inside a panel
Some applications scroll a central message list, document pane, or table while the surrounding webpage stays in place. The extension scrolls the main page; it does not independently traverse every nested scrolling container. A full-page result may therefore show only the current contents of that inner pane.
Use the visible-area option, scroll the inner panel yourself between separate captures, and keep the files clearly named. If the application offers an expanded view or its own export, that may better represent the panel's content. A scrolling screenshot is not a substitute for the application's underlying data export.
Sections repeat, disappear, or change halfway down
The extension captures the first view with fixed and sticky elements visible, then temporarily hides elements it identified with those positions for later views. This reduces repeated floating headers, but can also hide a sticky sidebar that you expected to see throughout the image. It attempts to restore the page styles and original scroll position after capture or an error.
Infinite feeds and pages that grow as you scroll do not have a reliable endpoint for this workflow. Content that loads late can create gaps or shift sections between frames. For a finite article, allow content to load first and retry. For a changing feed or dashboard, prefer smaller visible-area captures and record the needed context in your accompanying explanation.
The page is too large
This release rejects a full capture requiring more than 80 viewport frames. It also checks the estimated output against a 32,000-pixel limit per side and 80 million pixels in total. Display pixel density affects that estimate, so the same apparent page size can produce a larger image on a high-density display.
Switch to visible-area capture or use a shorter section of the source page. Do not assume that a page just under a limit will fit comfortably in every device's memory. If you already have a smaller successful capture, crop it to the useful content and export promptly.
The editor opens, but the result is incomplete
Inspect the top, middle, and bottom rather than relying only on the first screenful. Look for blank images, overlapping text, missing headings, and a cut-off final section. Then check the downloaded export too. An image PDF packages the capture into A4 pages; it does not repair capture gaps or preserve searchable webpage text. See the export format guide.
If the problem remains, save a local note with your browser version, capture mode, displayed error, and whether the page uses an inner scrolling panel. Use a non-sensitive example if you later report the issue. The help page includes a downloadable troubleshooting checklist. Export captures you need to retain: the extension prunes records older than 24 hours when a later capture starts, rather than providing permanent storage.