Hindi Website Screenshots Show Broken Matras? Chrome Font Fix
Broken Hindi matras in a screenshot can come from page rendering, system fonts, or capture. Use these checks to narrow down the cause before changing settings.
If Hindi vowel marks (matras) or conjuncts look detached, misplaced, or joined to the wrong character in a website screenshot, first find out where the problem appears: on one page or many, in the live page or only in the saved screenshot, and in one browser or several. Chrome’s zoom and font-size controls are useful checks, but they are not a guaranteed fix for Devanagari shaping.
Blurry text and broken matras are different symptoms. Google’s ClearType guidance is for fuzzy text on Windows; it does not establish a fix for incorrectly shaped Devanagari. Google’s text display troubleshooting covers text that appears as squares or looks blurry.
1. Locate where the rendering changes
Before changing settings, compare the same text in a few places. This is a practical way to narrow the cause, not a definitive diagnostic test.
- Open the page in Chrome and inspect the live text at normal zoom.
- Save or capture the page using the method that produced the bad image, then compare the same line with the live page.
- Open the same URL in another browser on the same device.
- If available, check the URL on a second device or operating system.
- Check another Hindi website in Chrome to see whether the symptom is limited to one site.
| What you find | What it suggests | Next step |
|---|---|---|
| Only one page is affected | The issue may be specific to that page’s fonts, styles, or content. | Compare another Hindi page and report the affected URL to its owner. |
| Several pages are affected in Chrome | A browser setting or platform font configuration may be involved. | Check Chrome’s appearance controls, then compare another browser. |
| The live page looks right; the saved screenshot does not | The capture path may differ from the browser view or timing. | Repeat the capture after the page and its fonts finish loading; compare a browser screenshot with the original capture method. |
| The live page and screenshot both look wrong across browsers | The page or the system’s font rendering may be involved. | Check another device and share the URL and platform details with the site owner. |
| Text is fuzzy but characters and matras are joined correctly | This is a clarity issue, not necessarily a shaping issue. | On Windows, follow Google’s ClearType and appearance guidance. |
2. Check Chrome zoom and font size
Chrome provides page zoom and font-size controls under Settings → Appearance. Zoom changes the size of the whole page; font size targets text. Google notes that changing font size does not work on every website. Treat these controls as checks, not as proof that a shaping problem has been fixed.
- In Chrome, open Settings.
- Select Appearance.
- Check Page zoom and return it to the expected value if it was changed accidentally.
- Review Font size. If you adjust it, reload the affected page and inspect the same text again.
- Compare with another Hindi page. If only one page remains affected, changing the global font setting may not help.
For the current controls and their limits, see Google’s instructions for changing text, image, and video sizes.
3. Separate fuzzy text from broken shaping on Windows
If the text is merely blurry or fuzzy on Windows, Google’s guidance includes checking ClearType and Windows appearance settings. Those steps address clarity. Do not assume they will repair a matra that is detached, misplaced, or joined to the wrong character.
If the letters are structurally wrong, continue the browser and device comparisons instead of repeating clarity adjustments. Record whether the same text is wrong in the live page, another browser, and another device.
Google’s text display troubleshooting describes the Windows-specific fuzzy-text guidance.
4. Understand what Chrome reset does
Resetting Chrome can be relevant if settings were changed unexpectedly, but it is not a complete font cleanup. Google says some settings, including font and accessibility settings, are not reset. If you have already reset Chrome and the matras remain broken, move on to comparing browsers and platform fonts instead of repeating the reset.
Review Google’s explanation of resetting Chrome settings before using this step, especially if you rely on customized browser settings.
5. Check system fonts on Linux when conjuncts are affected
A 2020 Google Chrome Help Community thread describes a Devanagari conjunct issue on MX Linux. The original poster first suspected Lohit Devanagari, then associated the problem with FreeSans and font substitution, and described a workaround involving substitution toward Noto Sans Devanagari. Other participants reported different observations involving Lohit Marathi and Blink. This is a limited community discussion, not an official diagnosis or a universal Chrome fix.
If the problem occurs on Linux across multiple pages or browsers, inspect the system’s installed Devanagari fonts and font substitution configuration. Make one change at a time and recheck the same sample text. Keep a note of the original configuration so you can undo a change. Do not apply a font substitution from that thread as a guaranteed fix for another distribution or version.
Read the MX Linux community discussion for its context and differing user reports.
6. If only the screenshot is wrong
When the live page looks correct but a saved image does not, identify which capture path made the image: Chrome’s own screenshot, an extension, automation, a remote browser, or a screenshot API. Repeat the capture after waiting for the page to settle and compare the same region. Check whether the capture was full-page or limited to a viewport, and whether the method applies a different viewport or device scale.
For a reproducible bug report, include the exact page URL, operating system, Chrome version, capture method, whether the live page is affected, and whether another browser or device shows the same result. A screenshot of the faulty line alongside the expected rendering helps distinguish a font-shaping issue from a capture-only difference.
7. Troubleshooting checklist
| Symptom | Likely area to check | Action |
|---|---|---|
| Characters appear as squares | Text display or missing glyph support | Use Google’s text display troubleshooting and compare another browser or device. |
| Text is fuzzy, but matras are correctly attached | Windows text clarity, if using Windows | Follow the ClearType and appearance guidance; do not treat it as a shaping fix. |
| Matras or conjuncts are malformed on one website | Page-specific font or rendering | Compare another Hindi page and report the exact URL to the site owner. |
| Several sites are malformed only in Chrome | Browser settings or browser/platform interaction | Check Appearance controls and compare the same pages in another browser. |
| Several browsers on Linux show a conjunct problem | System font configuration may be relevant | Inspect installed Devanagari fonts and substitutions; treat community workarounds as platform-specific clues. |
| Only an automated or saved screenshot is malformed | Capture timing or capture environment | Repeat after load completion and compare the capture environment with the live browser. |
| Resetting Chrome did not help | Reset does not clear all font settings | Continue with cross-browser and system-level comparisons. |
8. Make the diagnosis reproducible
Keep the investigation small and repeatable:
- Use the same URL and the same short passage for every comparison.
- Change one setting at a time, then reload the page.
- Note the operating system, Chrome version, zoom, and whether the issue affects live text or only an image.
- On Linux, record any font or substitution change before trying another one.
- When reporting the issue, include the comparison results rather than only saying that Hindi looks broken.
This avoids treating a change in text size or screenshot scale as evidence that the underlying shaping issue is resolved.
9. Or skip the browser setup
If your goal is to capture a clean website image without configuring browser automation, ScreenshotNeo is a website screenshot API and MCP server. It can return PNG, JPEG, WebP, or PDF from one GET request. See the ScreenshotNeo API documentation for parameters and formats.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp
import requests
r = requests.get(
"https://api.screenshotneo.com/v1/shot",
params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
timeout=90,
)
open("shot.webp", "wb").write(r.content)
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
await Bun.write('shot.webp', new Uint8Array(await res.arrayBuffer()));
Replace the example URL with the page you need to capture. The Python example requires the requests package. The Node.js example uses fetch and Bun to save the response bytes; in another Node.js environment, write those bytes with your preferred file API.
- Cookie and consent banners, newsletter popups, and chat widgets are removed before capture; each step can be turned off.
- Bot checks and CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed. Response headers report the page verdict and billing status.
- An MCP server provides
take_screenshot,get_page_info, andcapture_pdffor AI agents and MCP clients. - The free plan includes 1,000 screenshots per month with no card. Paid plans start at $5 for 3,000 screenshots.
Sign up for 1,000 free screenshots a month, with no card.
10. FAQ
Will increasing Chrome’s font size repair a broken matra?
Not necessarily. It changes text size, and some websites do not respond to that setting. Recheck the shaping itself after any change.
Does resetting Chrome restore every font setting?
No. Google says font and accessibility settings can remain after a reset.
Is a broken screenshot proof that Chrome rendered the live page incorrectly?
No. Compare the live page with the saved image and, if possible, repeat the capture using another method.
Should I install a different font immediately?
First establish whether the problem is limited to Linux, Chrome, one site, or the capture output. A community workaround is not a universal prescription.
What details help someone investigate the problem?
Share the page URL, operating system, Chrome version, capture method, whether live text is affected, and the results from another browser or device.


