Get help
For installation, webpage, PDF, OCR, account or Early Access problems, email:
This is the current support contact for Open Early Access. No guaranteed response time is offered during Early Access.
What to include in a bug report
- Dyslexly version and Chrome version.
- Whether the problem occurred on a webpage, native-text PDF, scanned PDF or Reading View.
- The exact action you took and what you expected to happen.
- The status shown by Dyslexly, such as Active, PDF only, Blocked or PRO · PAUSED.
- A screenshot with personal, document and account information removed.
Quick help
Dyslexly does not change a page
Check the exact status in the popup or Studio. Chrome internal pages, the Chrome Web Store, editable fields, code surfaces and blocked sites are intentionally not transformed. If the status is PDF only, choose a target that includes Web.
A font does not apply
Try Page font or System UI to confirm the page can be transformed. Some fonts do not contain every script; Dyslexly keeps an unsupported whole word in Page/System font rather than mixing glyphs inside the word.
PDF does not open in Dyslexly
Top-level PDF routing requires Chrome 151 or later, explicit PDF consent, a target that includes PDF, global ON and effective Pro. Embedded PDFs are not supported in this release.
The account says this build is not authorised
The installed extension ID is not on the Dyslexly server allowlist. Install the reviewed build or contact support with the Extension ID shown by Chrome. Do not send an OTP or session token.
Account data and policies
To request a copy or deletion of server account data, email from the address used for your Dyslexly account. Reading configuration stored locally in Chrome is separate and is not removed by signing out or deleting server account data.
Read the Privacy Policy and Terms of Use.