Frequently Asked Questions

ReadThisAloud is a Windows desktop reading application that converts supported documents and text into natural-sounding narration while keeping the spoken words visually connected to the text through synchronized highlighting and navigation tools.

It is designed to make longer or text-heavy material easier to consume by letting you listen while following the text. It can be useful for reports, training material, policies, instructions, research, study material, business documents, and everyday reading.

No. The normal workflow is straightforward: open or paste content, choose a voice, start narration, and use the visible reading and playback controls as needed.

ReadThisAloud is primarily a Windows desktop application. ReadThisAloud.com provides the website, customer account, licensing, secure downloads, product information, billing access, and related services.

Licensed customers receive access to approved software downloads through the ReadThisAloud customer account area. For security, use official downloads provided by ReadThisAloud.com rather than third-party download sites.

Yes. Visit the Demo page to view the real application workflow and guided demonstration. You can also review the Features and Voices pages before selecting a plan.

When a trial is available, the current trial length, narration allowance, eligibility, and any conversion-to-paid terms are shown on the Pricing page and during enrollment. Those current checkout terms control if they differ from older promotional material.

ReadThisAloud is currently designed for supported Microsoft Windows computers. Review the System Requirements page for the current supported Windows versions and hardware requirements before installing.

The current desktop application is designed for Windows. A native macOS version should not be assumed unless ReadThisAloud specifically announces one.

The current ReadThisAloud desktop software is a Windows application. Mobile and Chromebook versions are not part of the current desktop product unless specifically announced in the future.

Yes, provided your organization permits the installation and the computer meets the system requirements. Some corporate environments restrict software installation, cloud communication, or firewall access, so your IT department may need to approve or deploy it.

Installation requirements can depend on the Windows environment and how your organization manages software. If Windows requests administrator approval or your company restricts installations, contact your administrator or IT team.

Security products can occasionally block newly installed applications or network communication. Always download ReadThisAloud from the official site. If a corporate security product blocks the application, your IT team may need to review and approve the executable or required network access.

The exact requirement can change as the application is updated. Use the System Requirements page for the current installation and storage guidance. Exported WAV audio files may also require additional local disk space.

ReadThisAloud is designed to work with supported PDF documents, Microsoft Word documents, TXT files, and text that you paste directly into the Reader.

Yes. If you do not need to open a file, you can paste supported text directly into ReadThisAloud and begin a reading session from that content.

Yes, supported text-based PDF documents can be opened for narration. PDF formatting and text extraction vary widely, so the reading order produced by a PDF can depend on how the original PDF was created.

An image-only scanned PDF may not contain selectable text for the Reader to narrate. Unless OCR capability is specifically provided in the installed version, the document may first need to be converted into searchable/selectable text using OCR software.

Yes, supported Microsoft Word documents can be opened for reading. Very complex layouts, embedded objects, unusual formatting, or protected files may affect how text is extracted or displayed.

Yes. Plain-text files are supported and are generally one of the simplest formats for narration.

Reading a document in ReadThisAloud is not intended to rewrite the original source document. The Reader works with the content for display, navigation, narration, and related reading functions.

No document reader can guarantee identical extraction from every file. Password protection, malformed documents, unusual fonts, columns, tables, headers, footers, embedded objects, image-only content, or complex layouts can affect how text is extracted and presented.

You should use ReadThisAloud only with information you are authorized to process. Because natural narration can involve cloud speech processing, organizations with confidential, regulated, classified, medical, payment-card, or other specially protected information should review their own policies and the ReadThisAloud Privacy Policy and Security information before use.

ReadThisAloud uses modern neural text-to-speech technology delivered through its speech-service infrastructure. Neural speech models are designed to produce more natural pacing, pronunciation, and expression than older computer-generated voices.

ReadThisAloud may use Microsoft Azure Speech Services and other ReadThisAloud-controlled service components to provide supported natural voice narration. Customers interact with ReadThisAloud rather than entering Azure credentials into the desktop application.

No. Under the standard ReadThisAloud service, customers do not need to create, configure, or maintain their own Microsoft Azure Speech account.

No. Production cloud credentials are not intended to be supplied to or stored by the customer. The application communicates with ReadThisAloud services, which handle authorized speech requests.

Yes. The available voice choices are presented by ReadThisAloud. The exact catalog can change as voices are added, improved, removed, renamed, or changed by the underlying speech provider.

Where voice-preview functionality is available, you can use it to hear a sample before deciding which voice you prefer for a reading session. Visit the Voices page for the current voice experience.

No. Neural voices are very capable, but no text-to-speech system can guarantee perfect pronunciation of every name, acronym, abbreviation, specialized term, number, symbol, or unusual spelling. Important narration should be reviewed before it is relied upon or distributed.

Pronunciation is determined by the text, surrounding context, punctuation, language model, and speech provider. Acronyms, all-capital text, abbreviations, unusual punctuation, and uncommon names can be interpreted differently by the voice.

Yes. ReadThisAloud may add, remove, substitute, or modify voices for technical, quality, legal, licensing, security, or provider-related reasons.

Yes. Synchronized word highlighting is designed to keep the active spoken word visually connected to narration as the reading session progresses.

It helps you follow exactly where the narration is in the document. This can make it easier to read and listen together, regain your place after looking away, and move through dense material without treating the audio and text as separate experiences.

ReadThisAloud includes click-to-jump style navigation so supported text can be used to move the reading position to another location rather than requiring you to restart the narration from the beginning.

Yes. Bookmarks are designed to let you save useful positions and return to them later during your document-reading workflow.

Yes. Playback controls include speaking-speed adjustment so you can choose a pace that works better for the material and your listening preference.

Yes. ReadThisAloud provides volume control as part of the narration controls. Your Windows system volume and speaker/headphone settings also affect the final listening level.

Yes. Standard playback controls are designed to let you pause, resume, stop, and move through the reading session without losing the document itself.

Reading Mode is designed to provide a more focused reading environment for longer sessions, keeping the document and narration experience clear and easier to follow.

Progressive narration is designed to process longer material in manageable segments so narration can begin without requiring the entire document to be synthesized as one large audio job first.

Yes. The Reader includes playback and timeline controls designed to help you understand and manage the current narration position.

An internet connection is required for cloud-based natural voice synthesis and for functions that need ReadThisAloud account, licensing, or service communication. A loss of connectivity can prevent new cloud narration from being generated until connectivity is restored.

The natural voices are generated using cloud speech infrastructure. The necessary text is securely sent through the ReadThisAloud service for authorized speech synthesis and the resulting audio is returned for playback.

No. The intended production architecture keeps Azure and other protected service credentials on controlled backend infrastructure rather than distributing cloud keys to customer computers.

Previously received or locally available audio may continue depending on the current session, but new cloud narration may be unable to generate until connectivity returns. Exact behavior can depend on what content has already been processed.

Do not assume full offline operation. Natural neural speech generation relies on online services. Any offline grace or previously generated playback capability is subject to the functionality of the installed version and applicable licensing rules.

Possibly. Corporate networks may restrict outbound internet connections. If ReadThisAloud cannot activate or generate narration on a managed business network, your IT team may need to review the application’s permitted network access.

No. As described in the EULA, using a document with ReadThisAloud does not transfer ownership of your document to ReadThisAloud.

Text necessary to provide requested natural narration may be transmitted through ReadThisAloud-controlled infrastructure and supported cloud speech providers. Review the Privacy Policy for the current data-handling disclosures.

The production design is intended to keep protected Azure speech credentials and private service keys off customer computers. Customers should never need to know or enter ReadThisAloud’s backend cloud credentials.

ReadThisAloud uses Stripe for payment processing. Payment-card details are handled through Stripe’s payment infrastructure rather than being intentionally stored as raw card numbers by the ReadThisAloud application.

Account and service records may include information needed to manage your customer account, license, subscription, device activations, software version, usage totals, support, transactions, and related service functions. The Privacy Policy provides the controlling data-handling details.

Do not assume that ReadThisAloud is authorized for a specialized regulatory environment unless ReadThisAloud has expressly entered into the required written agreement and provided the required safeguards. Organizations handling regulated health, classified, payment-card, or similarly restricted information should obtain appropriate approval before use.

Visit the Security page and Privacy Policy. Business customers with specific security-review requirements can also contact the ReadThisAloud team.

A customer account is used for licensing, subscription status, secure downloads, device activation, and other account-related services associated with paid or trial access.

ReadThisAloud is designed to validate the customer’s authorized license through ReadThisAloud services rather than requiring customers to manage cloud-provider keys themselves.

The number of permitted devices depends on the plan you purchase. Review the current Pricing page and your account for the device allowance associated with your license.

Individual licenses are intended for the licensed user and may not be shared, pooled, resold, or distributed beyond the rights granted by the applicable plan. Business plans can provide separately assigned seats for authorized users.

Your licensing system may allow a permitted device to be deactivated or reassigned so the license can be used on a replacement computer, subject to your plan’s device limits and anti-abuse controls.

Contact Support. After account verification, the support team can review available options for an inaccessible or failed device activation.

Yes, provided your license remains valid and the reinstallation complies with your plan’s device and activation limits. Use the official installer made available through ReadThisAloud.

Use the password-recovery option provided in the customer account area. Never send your password to ReadThisAloud support. Support should not need your password to assist with your account.

As described in the EULA, a license or service may be suspended for reasons such as nonpayment, fraud, material license violations, security abuse, or unauthorized circumvention of licensing and service controls, subject to applicable law.

ReadThisAloud uses Stripe as its payment processor for supported online payments.

Payment-card entry is handled through Stripe’s payment infrastructure. ReadThisAloud may receive transaction-related information needed to manage your purchase, but the site and application are not intended to store your raw full card number.

If you choose an automatically renewing plan, the renewal frequency and price are disclosed during purchase. The subscription continues until canceled in accordance with the checkout terms, account controls, Terms of Service, and applicable law.

Use the cancellation method provided in your ReadThisAloud account or the method stated in the purchase terms. Unless otherwise required by law or stated at checkout, cancellation prevents future renewal and normally takes effect at the end of the current paid billing period.

When a subscription license expires, subscription-based activation and cloud-service access may end. Your account may remain available for permitted account functions, receipts, history, or future reactivation.

Plan-change availability, upgrade timing, billing adjustments, and any prorated amounts depend on the account and checkout system in use. The current options presented in your account control.

Some plans may include a monthly or per-user natural narration allowance. Current allowances are shown on the Pricing page and in the applicable purchase terms.

Depending on the plan and current product offering, you may need to wait for the next usage period, upgrade your plan, or purchase an available add-on. Your account should show the options available at that time.

If a renewal payment is declined or cannot be completed, ReadThisAloud may ask you to update your payment method and may suspend paid functionality or license access if payment remains unresolved, subject to required notices and applicable law.

Refund eligibility is governed by the Refund Policy, the terms presented when you purchased, and any rights that cannot legally be waived. Review that policy before purchasing.

Online purchases processed through the payment system can generate transaction confirmation or receipt information. Your ReadThisAloud account may also provide access to billing records supported by the current account system.

Applicable sales, use, transaction privilege, or similar taxes may be calculated based on the purchase and customer location where required. The final checkout amount controls.

Yes. ReadThisAloud includes export-to-WAV capability so supported narration can be saved as a WAV audio file when permitted by your license and the content you are using.

WAV is a widely supported audio-file format commonly used on Windows and in audio-editing applications. WAV files can be larger than highly compressed formats because they are typically stored with little or no lossy compression.

Yes. Once a permitted narration has been exported as a standard WAV file, it can generally be played by compatible audio players without keeping the Reader open.

No. Exporting narration does not create new rights in the original text. You remain responsible for having the legal right to use, reproduce, distribute, publish, or otherwise use the source content and resulting audio.

Your ability to publish, sell, monetize, or distribute Generated Audio depends on your rights in the underlying content, applicable law, the EULA, your plan, and any relevant third-party voice-service terms. Do not assume that owning a document copy gives you commercial audio-distribution rights.

No deceptive impersonation, fraud, unlawful misrepresentation, or violation of another person’s privacy or publicity rights is permitted.

Yes. Business licensing is intended to support organizations that need multiple authorized users or centrally managed purchasing. Visit Pricing or Contact for current business options.

Not unless the purchased plan expressly allows that model. Business licensing is generally managed by seats or authorized users so the organization should purchase enough licenses for its intended users.

Business deployment requirements can vary. Organizations with managed Windows environments should contact ReadThisAloud to discuss installation, licensing, firewall, security-review, and deployment needs.

Yes. ReadThisAloud can be considered for training, learning, document-review, facilitation, and other business reading workflows, subject to the purchased license terms and the organization’s information-security policies.

Business and organizational purchasing can be discussed with the sales team. Contact sales@readthisaloud.com for current options.

Yes. Business customers with procurement, licensing, deployment, privacy, or security-review questions can contact ReadThisAloud before purchasing.

First confirm that Windows audio is not muted, the correct speaker or headset is selected, ReadThisAloud volume is turned up, and another application can play sound. Then confirm that your internet connection is available for new natural narration.

Check your internet connection, license/account status, selected voice, document text, and whether security software or a firewall is blocking service communication. Restarting the application can also clear a temporary session issue.

Text-to-speech pronunciation depends on spelling, punctuation, context, abbreviations, capitalization, language, and the selected voice. Names, acronyms, technical terms, and uncommon words are the most likely to be interpreted differently than expected.

Synchronized highlighting depends on the relationship between extracted document text and speech timing. Unusual document formatting, complex text extraction, special characters, or unexpected segmentation can affect the visual location. If the issue is repeatable, send Support the document type, Reader version, and a clear description of where it occurs.

Some PDFs store text in an internal order that differs from what appears visually on the page, especially multi-column layouts, forms, tables, and documents produced by certain publishing tools. This is a characteristic of the PDF’s text structure rather than only its appearance.

If the PDF contains page images but no selectable text, the Reader may have no text to narrate. Convert the scan to searchable text with OCR first unless OCR support is specifically included in your installed version.

Confirm that the computer is online, your account is in good standing, you have not exceeded the permitted device count, and your firewall or security software is not blocking service access. If the problem continues, contact Support.

Voice catalogs can change because of provider updates, regional availability, quality changes, licensing changes, technical requirements, or ReadThisAloud product decisions. Select another currently available supported voice.

Larger documents require text extraction, segmentation, network communication, and speech generation. Progressive narration is intended to reduce the need to wait for an entire long document to be processed before useful playback begins.

Check that the narration is available, the destination folder is writable, there is enough disk space, and your plan/version permits the export function. Windows folder permissions or security controls can also prevent a file from being written.

Include your ReadThisAloud version, Windows version, what you were trying to do, what happened instead, the exact error message if one appears, whether the problem can be repeated, and the document type involved. Do not send passwords, full payment-card numbers, Azure credentials, or other secrets.

Visit the Support page or email support@readthisaloud.com.

Email sales@readthisaloud.com or use the Contact page for plan, licensing, team, and commercial questions.

Use the billing contact information provided on the Contact page for subscription, invoice, charge, and payment questions.

ReadThisAloud may provide maintenance releases, fixes, security updates, compatibility updates, and feature improvements. Some updates may be necessary for continued compatibility with licensing or cloud speech services.

Whether a particular update, upgrade, or future feature is included depends on the plan and product terms in effect at that time. Maintenance updates may be treated differently from major future product releases.

The ReadThisAloud End User License Agreement (EULA) explains the rights and restrictions that apply to the desktop software license.

Visit the Terms of Service for terms governing the website, accounts, subscriptions, and related services.

Visit the Privacy Policy for information about personal data and service-related processing.

Visit the Refund Policy for the current refund rules and eligibility.

ReadThisAloud is based in Phoenix, Arizona, United States.

No. ReadThisAloud is a reading and narration tool. It does not provide legal, medical, financial, safety, educational, or other professional advice, and synthesized narration should not replace review of important source material.

Contact us with your question. For technical problems, start with Support. For purchasing or business licensing, use Contact or email Sales.