What an HTML capture leaves out: whatever a script would have drawn
What an HTML capture leaves out depends on how much of the page is built by script. In Page to picture, the page is read as markup and painted from that markup. Script does not execute in this browser. Anything added after load never reaches the image.
Everything written in the markup is there: headings, paragraphs, tables, borders, background colour, type size, line height, images that are part of the document. Everything a script did later is not: the second slide, comments that open on click, a list that fills in as you scroll, a notice that appears after you submit. This is not a quality problem. That block of content was never in the markup.
Page to picture takes static content only. Scripts do not run, pages behind a sign-in do not appear, and images from another domain do not appear.
The page freezes at its first paint
A carousel driven by script comes out as its first slide. An image that loads on scroll comes out as empty space. A panel that opens on a button click is not in the picture at all. If the sentence you need only exists inside that panel, this tool will not get it for you.
A page behind a sign-in does not appear either. Ask for content you can only see after logging in and you get the login box, or nothing. ReadyIMG has no sign-in and no account server that receives images, and it will not log in to any site on your behalf. Here the only thing read is the public markup this browser can reach.
Images from another domain come out blank
If a picture on the page is served from a different domain, those pixels cannot be read while the capture is drawn, and the space stays empty. Images on the same site come out fine. A white gap, a broken frame, or a bare border is usually this, not a damaged file.
- Script-built content: the second slide, comments that open on click, lists that fill in on scroll.
- Pages behind a sign-in: you get the login box, or blank space.
- Images from another domain: the space stays empty, with only a border or a gap.
When the address cannot be read, paste the HTML
Some pages have no readable address in the browser: a file still on your disk, a page that only opens inside a private network, a fragment assembled on the fly. Paste the HTML source instead. It is the same static markup, and the same things still go missing.
Treat the viewport width as starting at 320. Narrow and wide are two different layouts, so the same page captured at each will not look alike. Decide who the picture is for first. For a phone, capture narrow.
Three ways out, pick one
You can get JPG, PNG, or an SVG that wraps a pixel image. For screenshots, text-heavy pages, or anything going into a document, keep PNG; letter edges stay cleaner. For a place that only accepts JPG, choose JPG. That SVG is a wrapper around pixels, not a vector that scales forever. Enlarge it and it blurs like any bitmap.
If the result is too heavy to send, run it through Shrink file. That works on the copy you just downloaded. The page you captured is untouched.
Page to picture handles one page at a time. It does not take a batch of 40 files. Finish a page, download it, then start the next.
What this picture is good for
Freezing a layout for someone who will not open a link. Keeping a record of how a page looked, in case it changes tomorrow. Putting a page into a document so the reader never has to leave it. All of that works.
It is a poor fit for capturing a process: mid-scroll animation frames, loading skeletons, a hover state. Those need script to run, and here script does not run.
Only two things touch the network
When you open the page, the visit is counted by 51.LA. What gets counted is that someone opened a page, not your image files. How files are handled sets that boundary: images are not uploaded to ReadyIMG, and there is no sign-in here.
The other is the first use of cutout, which downloads a recognition model into this device's cache. That is a different tool and has nothing to do with capturing a page. The work stays on this machine, and what you download is a new file made here.
Three looks before you send it
- Is any text cut off. A wide layout squeezed into a narrow viewport tends to break headings into three lines.
- Is any image missing. If so, capture again with a picture served from the same site.
- What you saved is a new file. The page and the original images are still where they were.
The queue lives only inside this one visit. Refresh or close the page and anything not downloaded is gone. Take the picture you want before moving to the next page.
If you have not started, go back to the bench, paste an address or some HTML, and open Page to picture. By now you should be able to name what your picture is missing.