pdfreaders.org

A PDF invoice in legal billing is a fixed-format document that presents the fees and costs owed on a matter in a layout that looks the same on every device. It is the digital equivalent of a printed bill: readable, portable, and easy to attach to an email or upload to a client portal. Its main limitation is that it is not machine-readable in the way a LEDES file is, so a client's e-billing system cannot automatically ingest it. PDF works best for flat-fee matters, small or one-off engagements, and clients who do not run an automated billing platform.

What "PDF" means in a legal billing context

When a billing tool offers to send an invoice "in PDF," it is generating a rendered document rather than a structured data file. The distinction matters:

• PDF is a presentation format. A human reads it. Line items, totals, and matter details appear as text and tables on a page.
• LEDES (Legal Electronic Data Exchange Standard) is a structured, delimited text format. An e-billing system parses it, validates it against outside counsel guidelines, and routes it for review.
• Email delivery is a transport method, not a format. You can email a PDF, email a LEDES file, or email a link to an online invoice.

These three are often confused because a single invoice can combine them: a LEDES file delivered by email, or a PDF attached to an email. The format is what the client's systems can read; the delivery method is how it arrives.

When a PDF invoice is the right choice

PDF is usually appropriate when the client does not require electronic submission through a billing platform. Common scenarios:

• Flat-fee and fixed-price matters. When the invoice is one or two lines, a structured file adds no value.
• Small businesses and individuals. Clients without an accounts payable system can open a PDF and pay from it.
• Retainers and replenishment requests. A simple statement of the retainer balance is easy to read as a PDF.
• Pro bono or courtesy bills. Where no formal e-billing review applies.
• Backup documentation. Even when a LEDES file is submitted, a PDF is often attached for the reviewer's convenience.

If the client has outside counsel guidelines requiring LEDES submission, a PDF alone will typically be rejected or returned for manual entry. Check the client's billing requirements before choosing the format.

PDF versus LEDES versus emailed invoice: a quick comparison

Core elements of a compliant legal PDF invoice

A PDF invoice should stand on its own. If a client's AP department picks it up with no context, it should still answer who, what, when, and how much.

Firm and client identification

• Firm name, address, and contact details
• Tax or VAT identification number where applicable
• Client name and billing contact
• Invoice number and invoice date
• Client matter number or reference

Matter and timekeeper detail

• Matter name and description
• For each timekeeper: name, initials, and billing rate
• Time entries with date, narrative description, and time recorded in tenths of an hour
• Clear separation of fee earners if rates differ

Fees, expenses, and totals

• Fees subtotal
• Disbursements and expenses, itemized with dates
• Taxes applied
• Prior payments, credits, or trust retainer applied
• Total amount due and currency

Payment terms

• Due date and payment window
• Accepted payment methods
• Remittance details or a payment link
• Late-payment terms if the engagement letter specifies them

A useful test: hand the PDF to someone who has never seen the matter and ask them to confirm the amount due and the period covered. If they hesitate, the invoice is missing something.

Practical limitations to plan around

PDF invoices shift work to the recipient. Someone at the client has to read the document and key the data into their system, which introduces delay and transcription errors. PDFs also cannot be validated against billing guidelines automatically, so a reviewer may reject a line item that a LEDES rule would have caught before submission.

Two habits reduce the friction:

1. Send a consistent template. Clients learn where to find the total, the matter number, and the payment terms.
2. Keep a LEDES version in reserve. If a client later adopts an e-billing platform, you can convert rather than rebuild.

Choosing between PDF, LEDES, and email delivery

Work from the client's requirements backward:

• Does the client mandate LEDES submission? If yes, PDF is a supplement, not a substitute.
• Is the matter flat-fee or very small? PDF is usually sufficient.
• Does the client have no billing system? PDF delivered by email or portal is the simplest path.
• Is the invoice complex with many timekeepers and expenses? A structured format reduces disputes, even if the client accepts PDF.

When in doubt, ask the client's billing contact which format they prefer and whether a PDF attachment is acceptable alongside any required file. That one question prevents most rejected invoices.

Easy Legal Billing supports sending or scheduling invoices in LEDES, email, or PDF formats, which lets you match the format to each client's requirements rather than forcing one approach across every matter.

pdfreaders.org is a directory site that lists Free Software PDF readers across major operating systems. It exists to help you choose a PDF viewer that respects the four freedoms — to use, study, share, and improve the software — rather than proprietary alternatives whose internal workings are trade secrets. If you want a PDF reader you can inspect, redistribute, or modify, and you care about keeping control over your own privacy and data, this site is aimed at you.

What the site actually provides

The homepage is a curated list of PDF readers, each with a short description and its supported platforms. It does not host the downloads itself; it points to project pages and assumes you will usually install through your operating system's package manager.

The site also makes an argument, not just a list. It notes that PDF exists in several versions — some qualifying as Open Standards, some certified by ISO, and some encumbered by software patents — and encourages promoting the Open Standard versions because Open Standards guarantee interoperability, competition, and choice.

The readers listed

How to use it

1. Identify your operating system.
2. Scan the platform column for readers that match.
3. Pick based on your secondary needs — for example, SumatraPDF if you want something small and fast on Windows, Okular if you need extra document formats, or sioyek if you read research papers and technical books.
4. Install through your distribution's package manager where possible. The site notes that most Free Operating Systems provide package management and do not require manual downloads from project pages; your distributor's website has the instructions.
5. Go to the project's download page only if you want source code to build the software yourself.

What it is not

• It is not a download host. Files come from the individual projects or your package manager.
• It is not a comparison of features, speed, or rendering quality. Descriptions are brief and platform-focused.
• It does not cover proprietary readers except to note that alternatives to Adobe's reader exist but, like Adobe's, keep their internal workings secret and do not respect your right to control your own privacy and data.

Who should use this list

Choose from this list if software freedom and privacy are your priority and you want a reader you can study, share, and improve. If you mainly need a specific proprietary feature, or your organization mandates a particular viewer, this list will not settle that question — it is a starting point organized around licensing and platform, not around feature benchmarks.

pdfreaders.org recommends only Free Software PDF readers because those programs respect the four basic freedoms — to use, study, share, and improve the software — which the site argues gives you control over your own computer and helps protect your privacy. The site frames this as a deliberate choice rather than a neutral software directory: it also warns that proprietary alternatives, including Adobe's reader, keep their internal workings as trade secrets and "do not respect your right to control your own privacy and data."

The two arguments behind the recommendation

The site makes two distinct points, and it helps to keep them separate.

1. Software freedom as user control. Every reader on the list is Free Software, which the site defines by the four freedoms: use, study, share, and improve. The claim is that this legal and technical status is what gives you control over your computer and protects your privacy — not any specific feature.

2. Open Standards as a separate concern. The site also discusses PDF versions, noting that some qualify as Open Standards, some are ISO-certified, and some are "encumbered by software patents." It argues you may want to promote the Open Standard versions because Open Standards "guarantee interoperability, competition and choice." This is about the format, not the reader — a Free Software reader and an Open Standard PDF are two different things the site cares about.

What the site actually lists

The recommended readers, with the platforms given on the page:

A few details from the page worth noting:

• Xpdf carries a caveat. The site states that "the XpdfReader builds are non-free, we advise against them" — so the project is listed, but a specific distribution of it is not endorsed.
• sioyek is described as designed for reading research papers and technical books, which makes it the most task-specific entry on the list.
• Okular and Evince are the document viewers of the KDE and GNOME projects respectively and handle formats beyond PDF.
• SumatraPDF is described as powerful, small, portable, and fast to start.

Practical consequences if you follow this advice

The site adds an installation note that matters more than the list itself: most Free Operating Systems provide package management systems, so you generally do not need to download files manually from project pages. Installation instructions live on your distributor's website. The download pages linked from pdfreaders.org provide source code if you want to build the software yourself.

So the practical path is: identify your platform, pick a listed reader, then install it through your distribution's package manager rather than chasing a binary from a project page.

When this recommendation may not fit you

The site's logic is coherent, but it is a values-based filter, not a feature comparison. If your priority is a specific capability — say, advanced annotation, form filling, or a particular accessibility workflow — the list does not rank readers on those grounds, and the page does not claim to. The recommendation answers "which readers respect my freedoms and privacy?" It does not answer "which reader is best for my document workflow?"

The site also invites contribution: it asks readers to help translate the interface or download pages of their favorite PDF reader, which signals that the list is maintained as a advocacy resource rather than a comprehensive catalog.

pdfreaders.org lists Free Software PDF readers by platform, and several run on more than one operating system. If you want a quick pick: SumatraPDF for Windows, Skim for macOS, and Evince, Okular, or Zathura for GNU/Linux. All of the readers below are Free Software, which the site defines as respecting your four basic freedoms to use, study, share, and improve the software — giving you control over your computer and helping protect your privacy.

Readers by platform

How to choose

• Windows only: SumatraPDF is the standout for a small, portable, fast-starting reader. If you also want a KDE-style viewer that handles extra formats, Okular is available for Windows too.
• macOS only: Skim is the listed option built specifically for OS X, including note-taking. gv and sioyek also run on Mac OS X.
• GNU/Linux: You have the widest choice — Evince, Okular, Xpdf, qpdfview, gv, sioyek, MuPDF, and Zathura.
• Cross-platform: Okular (GNU/Linux, Windows), sioyek (GNU/Linux, Mac OS X, Windows), MuPDF (GNU/Linux, Android, Windows), and gv (GNU/Linux, Mac OS X).
• Reading research papers or technical books: sioyek is described as designed for exactly that.
• Minimal and lightweight: Xpdf, gv, and qpdfview are described as lightweight or simple.

Installation notes

Most Free Operating Systems provide package management systems, so you usually do not need to download files manually from project pages. The site points you to your distributor's website for installation instructions. The download pages it links to provide source code if you want to build the software yourself.

Why only Free Software readers

The site recommends Free Software readers because they respect your four basic freedoms and give you control over your computer and your privacy. It notes that proprietary alternatives to Adobe's PDF reader exist, but like Adobe's, their internal workings are a trade secret and they do not respect your right to control your own privacy and data. The site also suggests promoting PDF versions that are Open Standards, since Open Standards guarantee interoperability, competition, and choice.

pdfreaders.org does not host installers itself. It lists Free Software PDF readers and points you to each project's own download page, but the site notes that most Free Operating Systems provide package management systems, so you usually do not need to download any files manually from project pages. Installation instructions live on your distributor's website, and the project download pages provide source code if you prefer to build the software yourself.

What pdfreaders.org actually gives you

The site is a directory, not a download portal. For each reader it lists the platforms it supports, and that platform list is the main thing you need before choosing an installation route.

Two notes from the site that affect what you install:

• Xpdf is listed as a lightweight viewer using a plain motif interface, but the site states that the XpdfReader builds are non-free and advises against them. If you want Xpdf specifically, this is a reason to check what you are actually installing.
• The site frames its whole list around Free Software, which it describes as respecting your four freedoms to use, study, share, and improve the software, giving you control over your computer and helping protect your privacy. It contrasts these with proprietary alternatives to Adobe's PDF reader, whose internal working is a trade secret.

Installing on GNU/Linux or another system with a package manager

This is the route the site itself recommends first. The steps are the same regardless of which reader you picked:

1. Identify your distribution and its package manager (for example, the package tool your distributor documents).
2. Open your distributor's documentation for installing packages.
3. Search for the package name matching your chosen reader — for example, Evince, Okular, qpdfview, or Zathura.
4. Install it through the package manager rather than from a project page.
5. Verify by opening a PDF with the newly installed reader.

Expected result: the reader is installed, tracked by your package manager, and updated along with the rest of your system. The common snag is a package name that differs slightly from the project name, so check your distributor's package index rather than assuming the project name is the package name.

Installing on Windows or macOS

For these platforms the package-manager shortcut usually does not apply, so you go to the project's own download page. The site's platform list tells you which projects to look at:

• Windows: SumatraPDF, Okular, sioyek, MuPDF
• macOS: Skim, gv, sioyek

The practical sequence:

1. Pick a reader whose platform list includes your system.
2. Go to that project's download page (linked from pdfreaders.org).
3. Download the build offered for your platform.
4. Run the installer or move the application into place, following the project's own instructions.
5. Verify by opening a PDF.

If a project offers only source code for your platform, you will need to build it — see below.

Building from source

The site states that the download pages it refers to will provide source code, should you desire to build the software. This is the fallback when no ready-made build exists for your system, or when you specifically want to compile it yourself.

Before starting, confirm you have:

• The source archive from the project's download page.
• The build dependencies the project lists.
• A working toolchain for your platform.

Then follow the project's own build instructions. The expected result is a locally built binary you run directly. The usual failure point is a missing dependency, which typically shows up as a configure or compile error naming the missing library.

Choosing between the two routes

A note on translation and contributing

The site also invites users to help translate the interface or the download webpages of their favorite PDF reader. That is separate from installation, but it is the site's stated way for users to contribute back to the projects it lists.