Quick start
- Open an ordinary webpage, Gmail message list, text-based PDF, or supported Google Doc.
- Select the iPage icon in the Chrome toolbar. The reader opens in Chrome's side panel.
- Use − and + to change the article text size.
- Keep Main on for the focused reading view, or turn it off to show all extracted content.
- Select Play to read the displayed text aloud, Translate to translate on request, or any preserved link to continue browsing.
Toolbar controls
| iPage logo | Identifies the reader and keeps the compact toolbar easy to recognise. |
|---|---|
| − A + | Decrease or increase article text size. Settings provides the full 16–48 px range and line-spacing control. |
| Sun / Moon | Switch between the warm light background and softened dark background. |
| Main | Show the main content only, excluding common navigation, footers, reactions, sharing controls, subscriptions, comments, author biography, and post-navigation sections. |
| Accessibility | Turn on larger controls, stronger contrast and focus, underlined links, wrapped toolbars, reduced motion, and shorter reading lines. |
| Play / Stop | Start or stop language-matched read aloud with live highlighting and automatic scrolling. |
| Translate | Translate only when selected. Select again to restore the original language. |
| Refresh | Request the latest readable content from the active tab. |
| Settings | Open text, speech, translation, accessibility, app information, support, and bug-report options. |
Supported content
Ordinary webpages
iPage extracts headings, paragraphs, lists, quotations, captions, tables, image descriptions, metadata, and safe links from pages Chrome permits extensions to read. Main-only mode removes common supporting regions without changing the original website.
Gmail
In the inbox, iPage presents useful sender, subject, and preview information. Select a subject inside iPage to open that Gmail message and display its readable body. Use the contextual Back control to return to the inbox view.
Text-based PDFs
iPage uses its packaged copy of PDF.js to extract embedded PDF text locally. It does not read the Chrome PDF viewer's thumbnail or document-navigation controls. Scanned image-only PDFs require OCR and password-protected PDFs must be unlocked first.
Google Docs
An open Google Doc can be read when its owner permits plain-text export. iPage requests that export through the signed-in Chrome session; it does not receive the user's Google password.
Links and navigation
Safe links kept inside the extracted text remain clickable. When a link changes the active page, iPage waits for the new page to become ready and refreshes the reading view. A contextual Back button appears only when there is a relevant iPage navigation history.
Read aloud
Automatic voice selection detects the displayed article language and chooses a compatible Google voice exposed by Chrome. Matching uses the BCP-47 language, script, and region so a Korean voice is not reused for an English page. You can choose another available Google voice and save a speech rate from 0.6× to 2×.
Long articles are divided into ordered speech-sized sections. As Chrome reports speech timing, iPage highlights the current text and scrolls it into view. Voice availability and timing precision depend on the Google voices exposed by the user's Chrome installation.
Translation
The original language is always the default. Translation begins only after the user selects Translate. iPage first attempts Chrome's built-in Translator capability. If inline translation cannot start, iPage can open Google Translate with the current page address and selected target language. The saved target language is used across iPage views.
Accessibility Assist
Accessibility Assist adds 44 px controls where practical, stronger contrast, a more visible keyboard focus ring, underlined links, wrapped toolbars, reduced motion, wider paragraph spacing, and a shorter reading line length. The iPage interface also uses semantic landmarks, labelled controls, keyboard focus, status announcements, and reduced-motion support.
Privacy
iPage has no developer-operated content server, iPage account, analytics, advertising, or behavioural tracking. Webpage, Gmail, PDF, and supported Google Docs content is processed in Chrome for the requested reading view and is not sent to the developer. Preferences are stored in Chrome storage and temporary article cache data remains only for the browser session.
Chrome or Google may process text when the user requests Chrome translation, opens the Google Translate fallback, or starts a remote Google TTS voice. Optional PayPal and Buy Me a Coffee links open only when selected. See the full iPage Privacy Policy.
Troubleshooting
“This page could not be read”
Refresh the webpage, wait for its main content to appear, then select Refresh in iPage. Chrome-protected pages such as the Chrome Web Store and chrome:// pages cannot be read.
The wrong page content is displayed
Select Refresh after navigation. iPage normally detects ordinary and supported single-page-app navigation automatically, but a site may delay or replace its content in an unusual way.
Some lazy-loaded content is missing
iPage prepares common scroll-triggered pages without changing the user's original scroll position. Content behind sign-in, a manual “load more” control, or an embedded cross-origin frame may remain unavailable.
A local PDF does not open
Open Chrome's extension details for iPage and enable “Allow access to file URLs.” The PDF must contain embedded text; scanned pages require OCR.
The selected voice is unavailable
Set Voice to Automatic (Google) or choose another Google voice shown by Chrome. Available languages and voices vary by Chrome installation and operating system.
Report a problem
Use Report a bug and include the page type, Chrome version, and a description of what iPage displayed. Do not include private email or document content.