Independent public-interest evaluations of how systems respect dignity and support agency.
HXR Case Record
ChatGPT Read Aloud Develops Progressive Static During Continuous Playback
A contributor reports that ChatGPT Read Aloud begins with clean audio, then develops progressively worsening static after roughly 60–90 seconds of continuous listening. Restarting playback temporarily clears the distortion, and the timing resets even when playback resumes from a later point in the same response.
- Case ID
- UXR-2026-0818-0001
- Case status
- Active Evidence Collection
- Reform status
- No Reform Demonstrated
- Resolution
- Unresolved
- Public revision
- 1
- Publication basis
- Anonymized With Contributor Approval
- Last updated
- August 18, 2026
Incident Case UXR-2026-0818-0001. This case documents a recurring ChatGPT Read Aloud audio-quality problem reported by one contributor.
What happened
The contributor reports that ChatGPT Read Aloud begins with clean audio. After roughly 60 to 90 seconds of continuous listening, static becomes audible and then grows progressively more pronounced as playback continues.
The contributor initially force-quit ChatGPT and restarted the same response. That temporarily restored clean audio. A more revealing observation came from restarting the app, seeking forward to a later point in the same response, and resuming playback there. The later content initially played cleanly, and the static returned only after another roughly 60 to 90 seconds of continuous listening.
The repeatable pattern
The reported trigger follows continuous playback time from the latest start or resume. It does not follow a particular sentence or absolute timestamp in the response. Moving to a later point in the same audio does not cause the static to reappear immediately. The contributor instead receives another interval of clean playback before the distortion returns and progressively worsens.
Same-device comparison
The contributor reports using the same device to listen to Gemini, Claude, Copilot, podcasts, Apple Music, and SiriusXM without encountering this progressive static. Those observations help define the reported user-facing boundary, but they do not independently establish what internal component causes the ChatGPT behavior.
Why it matters
Read Aloud is useful because it allows a response to be consumed continuously without keeping visual attention on the screen. Progressive distortion changes that experience. The listener must monitor audio quality, interrupt playback, restart ChatGPT, seek back to the intended position, and resume listening in order to temporarily restore intelligible audio.
Evidence and scope limits
The current evidence is contributor testimony. It supports the reported progressive-static pattern, the restart and seek observation, and the same-device comparison described above. Missing corroboration does not discount that testimony.
This Incident does not establish how common the behavior is, the exact ChatGPT or iOS version involved, the audio-output route, the responsible OpenAI team, or whether the cause is in ChatGPT, iOS, networking, Bluetooth, speech generation, streaming, buffering, decoding, or another component.
Evaluation graph
This Incident contributes evidence to UXR-EVAL-0014: ChatGPT Read Aloud Playback Continuity and Audio Integrity. The Incident preserves what happened to this contributor. The Evaluation is the living analytical record that can accumulate additional incidents, counterexamples, technical evidence, organization responses, and reform evidence over time.
Requested reform direction
ChatGPT Read Aloud should maintain stable, intelligible audio quality for the full duration of a response. Continuous session time should not cause progressively increasing static, and users should not need to restart or reseek playback in order to preserve audio integrity.
Acceptance test
Play multiple sufficiently long ChatGPT Read Aloud responses continuously, then begin additional runs from different seek positions. A passing result keeps the audio intelligible and free of progressively increasing static for the full playback duration. Restarting or reseeking should not be required to preserve audio quality.
Public discussion
Comments are moderated. A comment does not automatically become evidence, corroboration, a correction, or an organization response. Do not place private account information, medical information, or sensitive evidence in comments.