Recommended Free Tools
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Use Puppeteer’s page.screenshot({ fullPage: true }) to capture the full rendered page, and await document.fonts.ready first so font loading and related layout work have settled. That wait does not prove the intended font loaded or that it contains every Hindi glyph, so inspect the image when exact rendering matters.
Capture a full-page screenshot after fonts load
This runnable Node.js example navigates to a page, waits for network activity to become idle, waits for the document’s fonts, and saves a PNG:
import puppeteer from 'puppeteer';
const browser = await puppeteer.launch();
try {
const page = await browser.newPage();
await page.goto('https://example.com', { waitUntil: 'networkidle0' });
await page.evaluate(() => document.fonts.ready);
await page.screenshot({ path: 'page.png', fullPage: true });
} finally {
await browser.close();
}Puppeteer is a JavaScript library for automating Chrome and Firefox, and Chrome for Developers lists screenshots among its uses (Puppeteer ScreenshotOptions; Chrome for Developers: Puppeteer). The ScreenshotOptions reference documents fullPage; its default is false, so set it to true explicitly for a full-page capture.
networkidle0 is an example navigation condition, not a guarantee that an application has finished rendering. Some pages keep requests open or add content later. If the site has a known ready signal, wait for it before taking the screenshot.
#1 Best Overall
What the font wait guarantees—and what it does not
document.fonts.ready resolves when the document has completed loading fonts, layout operations are complete, and no further font loads are needed, according to MDN’s FontFaceSet.ready reference. Awaiting it helps avoid capturing while requested fonts or resulting layout changes are still in progress.
Font readiness is not proof that a particular font face loaded successfully, supports the Devanagari glyphs on the page, or visually matches the site’s intended design. The browser may render unsupported characters using fallback fonts. Inspect the screenshot for missing characters, inconsistent letter shapes, and unexpected line wrapping. If it differs from normal browsing, check the page’s CSS font-family and font requests in browser developer tools.
Rank #2
Handle late content and lazy-loaded sections
If the application inserts Hindi text after navigation, wait for an application-specific signal that the text is present. If the page loads sections or fonts only after scrolling or interaction, perform that action before capture, then wait for the resulting content and fonts again. These steps depend on the site; neither navigation-idle nor font readiness alone guarantees that content added later is ready.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →A small diagnostic variant logs the browser’s font-set status before capturing:
await page.goto(url, { waitUntil: 'domcontentloaded' });
await page.evaluate(() => document.fonts.ready);
const fontStatus = await page.evaluate(() => document.fonts.status);
console.log({ fontStatus });
await page.screenshot({ path: 'full-page.png', fullPage: true });The status is a useful diagnostic, not a check that the intended Hindi font or every glyph rendered correctly.
Choose an image or PDF
| Need | Puppeteer method | Important detail |
|---|---|---|
| Rendered page as an image | page.screenshot({ path: 'page.png', fullPage: true }) |
PNG is the documented default image type; set fullPage: true for full-page capture. See ScreenshotOptions. |
| Document output | page.pdf() |
PDF generation uses print media by default. To use screen styles, emulate screen media before calling page.pdf(). See Page.pdf(). |
A full-page screenshot is not simply a record of one viewport. For exceptionally long pages or pages with sticky or fixed elements, inspect the resulting dimensions and appearance; the documented option does not specify every edge-case layout outcome.
Or skip the browser setup
ScreenshotNeo can return a screenshot with one GET request. Its capture flow accepts cookie and consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each step can be turned off. Bot checks and CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and response headers report the page verdict and billing status. It also provides an MCP server with screenshot, page-info, and PDF tools for AI agents.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteHere is a cURL example using the documented API endpoint; replace the URL with the page you want to capture. See the ScreenshotNeo API documentation for options and response details.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpThe free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000. Sign up for ScreenshotNeo’s free plan.
Troubleshoot common rendering problems
- Hindi characters are missing or appear as boxes: Font readiness does not establish glyph coverage. Inspect the font requests and CSS font stack, and confirm the selected face supports the characters shown.
- The screenshot uses fallback-looking letterforms: Check whether the intended font request completed and whether the font was applied to the relevant text. Await
document.fonts.readyafter the content that triggers font loading is present. - Text wraps differently from the live page: Late font loading can change metrics and layout. Wait for fonts after late content or scrolling, then compare the capture’s layout with the browser page.
- The capture misses content added after navigation: A navigation wait condition cannot know an application-specific completion state. Wait for the relevant selector or app signal before capture.
- Navigation never reaches
networkidle0: The site may keep requests active. Use an appropriate alternative such asdomcontentloaded, then wait for the page’s own ready condition and fonts. - A long page or fixed element looks unexpected: Review the output dimensions and visual result. Full-page behavior with sticky or fixed elements can vary by page layout.
Frequently Asked Questions
Does document.fonts.ready confirm that the Hindi font loaded successfully?
No. It indicates that font loading and related layout work have settled; it does not verify a specific font face, Devanagari glyph coverage, or visual correctness.
Best Value
- Used Book in Good Condition
Should I use page.screenshot() or page.pdf()?
Use page.screenshot() for a raster image. Use page.pdf() for PDF output, accounting for its print-media default.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
