DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to capture a screenshot or PDF of a web page with Moli

Save a PNG or PDF of a rendered page for review, reports, or visual checks.

  • Research
  • Intermediate
  • 15 minutes
  • From the README
  • Any agent

Who it is forA QA tester or operations person who needs an image or PDF of a live page, triggered by a need for visual evidence.

The problemText extraction alone cannot show how a page looks, and most headless setups need a separate browser install to take pictures.

The outcomeA PNG of the viewport or the full page, or a paginated PDF, saved to a local file.

What you need first

  • A computer running Linux, macOS, or Windows
  • Terminal access (PowerShell on Windows)
  • Permission to download and run the Moli installer from GitHub
  • A URL to fetch or test

Steps

  1. Install the Moli binary from the README installer.
  2. Run moli fetch --layout --dump screenshot https://example.com > page.png for a viewport PNG.
  3. Run moli fetch --layout --dump pdf https://example.com > page.pdf to save a paginated PDF instead.

Prompt for your agent

Using the repo lexmount/moli, run `moli fetch --layout --dump screenshot <target-url> > page.png`. Save the PNG and report its file size. Verify that the file opens as an image showing the page.

Caveat. Visual output requires the --layout flag because layout and rendering are off by default, so screenshots will not appear without it.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page