Text to Speech for Lawyers: Review Documents by Ear

Most text-to-speech apps work like this: you send text to a remote server, the server generates audio, and it streams back to your phone. The text you sent lived on someone else's machine, however briefly. For a novel, nobody cares. For a client's merger agreement or a sealed filing, that is a confidentiality problem that most firms would flag immediately.

On-device TTS runs the entire process locally. The file stays in the app sandbox on your iPhone or Mac. The voice generation happens on your device's processor. No network call is made for speech. No account is created. Nothing is uploaded anywhere. This is the fundamental distinction we covered in on-device text to speech explained, and for legal work it is the difference between a tool you can use and one you cannot.

One honest note: you should still follow your firm's data-handling policies. On-device processing removes the cloud exposure, but it does not override your compliance obligations. What it does is remove the third-party problem that rules out most TTS apps for legal use.

Some legal documents are pure audio gold. Others are not. Here is a practical taxonomy:

• Opposing counsel's filings. You need the argument and the key cases. Listening at 1.3x during your commute gives you the shape of their position before you sit down with it.
• Contracts at the review stage. After you have seen the template, you are scanning for deviations. Audio catches surprising clauses that eyes sometimes gloss over.
• Witness statements and depositions. Narrative text reads naturally aloud. You will hear inconsistencies that look fine on the page.
• Long emails and memos. Save them as PDF, import, and listen while you walk to court.
• Dense statutory text with heavy citations. This is harder. Audio does not handle nested statutory references well. Save these for screen reading.

The whole setup takes two minutes and creates no external copies:

1. Download LoudReader from the App Store on your iPhone or Mac. Free, no account. No signup screen.
2. Import the document. On iPhone, share the PDF to LoudReader from Files, Mail, or your document management app. On Mac, use the file picker or drag and drop. The file copies into the app sandbox and never leaves.
3. Press play. Lock the screen. Playback continues, and the lock screen shows play, pause, and 15-second skip controls.
4. When you are done, the file stays in your LoudReader library. Delete it from the app when the matter closes. No cloud sync to worry about, no copies on a server you do not control.

For the Mac workflow specifically, see read EPUB aloud on Mac, and for PDFs on iPhone, listen to PDF on iPhone. The privacy model is the same on both platforms: local only.

Most DMS platforms let you export a PDF copy of a document. Export to your device, import into LoudReader, and listen. The exported PDF is a local copy that stays in the app sandbox. Delete it from the app when you are finished. This is the same handling you would give any local copy of a document, and on-device processing means the app itself does not introduce a new exposure point.

For the broader privacy model, our guide to private text to speech with no cloud walks through what on-device actually means and what it does not.

It depends on the brief and the task. For a first-pass read of the argument section, yes. You get the flow, the key cases, the rhetorical shape. For the section where you are going to write a response, you will want the text in front of you. Audio is a first pass, not a replacement for the close read.

The speed setting matters here. Legal prose is dense, and 1.0x is a sensible starting point. In LoudReader, speed control from 0.3x to 3.0x is a Premium feature; the free tier plays at normal speed. Many lawyers find 1.1x to 1.3x comfortable for familiar document types and 0.9x helpful for dense statutory language.