filepdf.net

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.

BentoPDF's Merge PDF tool combines multiple PDFs into one file entirely in your browser, so your documents never leave your device. It preserves bookmarks, requires no signup, and the site states there are no file limits. This works well when you want a quick merge on a laptop or desktop with a modern browser and don't want to hand your files to a server. If your PDFs are password-protected, corrupted, or you need to merge hundreds of large files, a desktop tool may still be the more reliable choice.

What "browser-based" merging actually means

Most online merge tools upload your files to a server, process them there, and send the result back. BentoPDF takes a different approach: according to the site, "all the processing happens locally on your device," with no uploads. The merge runs in your browser's memory using client-side code.

Two practical consequences:

• Privacy: Your files stay on your machine. Nothing is transmitted to BentoPDF's servers, which matters for contracts, invoices, medical records, or anything confidential.
• Limits come from your device, not the service: Since there's no upload step, there's no server-side file-size cap. The real constraint is your available RAM and browser tab stability. Merging a few dozen typical PDFs is fine; merging hundreds of very large scanned files in one tab can slow down or crash the browser.

The site also lists "No Signups," "Unlimited Use," and "Works Offline" as features, and describes itself as free and open source.

Step-by-step: merge your PDFs

1. Open the Merge PDF tool on BentoPDF (it's listed under Popular Tools on the homepage).
2. Add your files. Select the PDFs you want to combine. Because processing is local, the files load into the browser rather than uploading.
3. Order the files. Arrange them in the sequence you want in the final document. This is the step people most often get wrong — check the order before merging, since the output follows the list order.
4. Run the merge. The tool combines the PDFs into a single file. The site notes it preserves bookmarks, so existing bookmark structures carry over.
5. Verify the result. Before saving, confirm:
   • Total page count matches the sum of your inputs
   • Page order is correct
   • Bookmarks are intact (if your source files had them)
6. Save the merged file to your device.

Common failures and how to handle them

When to use a desktop tool instead

Browser-based merging is the better choice when you want privacy, no signup, and quick results on a normal-sized job. Consider a desktop application instead if:

• You routinely merge very large volumes (hundreds of files or multi-gigabyte scans) where browser memory becomes the bottleneck
• You need to merge password-protected files without first decrypting them
• You need advanced output control (specific compression, PDF/A or PDF/UA compliance, or automated batch pipelines)

BentoPDF does offer related tools — a PDF Multi Tool for merging, splitting, organizing, and rotating in one interface, and a PDF Workflow Builder for custom pipelines — so if your task is more than a simple merge, those are worth checking before reaching for separate software.

To split a PDF, open the file in a tool that supports page-level operations, choose whether you want every page as a separate file or one or more custom ranges, then export the selection as new PDFs. Soda PDF offers this through its desktop app, its browser-based Online platform, and a Google Chrome extension, so you can pick the route that matches where your file already lives. The steps below cover the general workflow, how to handle protected or scanned files, and how to confirm the output is correct.

When splitting a PDF is worth doing

Splitting makes sense whenever one large file contains material that different people or systems need separately:

• Extracting specific pages — pulling a signed page, an invoice, or a single chapter out of a long report.
• Separating chapters or sections — turning a book or manual into standalone documents.
• Reducing file size for email or upload — sending only the pages a recipient needs instead of the whole document.
• Reorganizing a scan — a batch scan often lands in one PDF, and splitting lets you file each document separately.

If you only need to remove a few pages rather than create new files, deleting pages may be faster than splitting.

Choosing a method

Soda PDF describes its desktop app as suited to uninterrupted offline work, while the Online platform is positioned for access from any device with cloud storage built in. If your PDF contains sensitive material and you would rather not upload it, the desktop route keeps the file local.

Step-by-step: splitting by page range or individual pages

The exact labels vary by tool, but the underlying flow is the same:

1. Open the PDF in your chosen tool — load it into Soda PDF Desktop, open it in Soda PDF Online, or use the Chrome extension.
2. Find the page organization feature. Soda PDF groups page-level actions under its Merge & Compress toolset, which the site describes as letting you "rearrange or delete pages from your PDFs with ease."
3. Select your split mode. Choose either:
   • Every page separately — produces one PDF per page.
   • Custom ranges — for example pages 1–5 as one file and 6–12 as another.
4. Define the ranges. Enter start and end pages for each output file. Double-check the numbering, since the first page of the document is page 1 regardless of any printed page numbers.
5. Run the split and export. The tool generates the new PDF(s). Save them to a folder you can find again.
6. Verify the output (see the checking section below).

Expected result: each range you defined becomes its own PDF containing exactly those pages, with the original file left untouched.

Handling password-protected and scanned PDFs

These two cases cause most split failures:

• Password-protected files. A tool generally cannot read or reorganize pages until the document is unlocked. Enter the password when prompted, or remove the protection first if you have the rights to do so. If you don't have the password, splitting isn't possible through normal means.
• Scanned PDFs. A scan is often just an image of a page, so the text isn't selectable. Splitting still works because it operates on pages, not text — but if you also need to search or edit the content afterward, run OCR first. Soda PDF's OCR tool "automatically scan[s] & recognize[s] text within an image" and can turn page ranges into editable PDFs.

Checking the split and avoiding quality loss

Splitting rearranges existing pages rather than re-rendering them, so page content, images, and formatting should carry over unchanged. To confirm:

• Open each output file and check the first and last page against the range you specified.
• Confirm the total page count matches the range size.
• Check that links, bookmarks, and form fields still behave as expected — these can occasionally point outside the new file's page set.
• If file size matters, note that splitting alone doesn't compress; use a separate compression step if the output is still too large.

Common snags

• Wrong pages in the output — usually a range entered against printed page numbers instead of the PDF's internal numbering.
• The tool won't load the file — most often encryption; unlock it first.
• Text won't select after splitting — the source was a scan; run OCR if you need editable text.
• Output looks lower quality — splitting preserves the original pages, so a quality drop usually means the file was re-exported or compressed somewhere in the chain rather than split.

For pricing and plan details, check the Soda PDF plans page, since feature availability can differ between the free tools and paid plans.

Free PDF tools let you merge, split, compress, convert, edit, annotate, and sign PDFs without paying for desktop software. The main decision is where the processing happens: browser-based tools that run locally on your device (like BentoPDF, which states all processing happens locally with no uploads, no signup, and unlimited use) versus cloud services that upload your file to a server. Local processing is the safer default for sensitive documents; cloud tools are worth considering only when you need heavy conversion engines or collaboration features a browser can't provide.

What free PDF tools actually cover

Most toolkits group their features into a few buckets. BentoPDF's own listing is a useful reference for what "100+ tools" typically means in practice:

If your task is on this list, a free browser tool can almost certainly handle it. If it isn't — OCR on scanned handwriting, complex form scripting, print production with precise color profiles — you likely need a paid or desktop tool.

Local vs. upload-based: the trade-off that matters most

This is the single biggest factor in choosing a free tool, and it's usually buried in the fine print.

Browser-based / local processing

• Your file never leaves your device, so there's no server-side copy to worry about.
• Works offline once the page is loaded (BentoPDF explicitly lists offline use).
• No signup wall and no per-file upload limits, since there's no server cost per file.
• Ceiling: performance depends on your device's memory and CPU, so very large files can be slow.

Cloud upload services

• Can offer heavier engines (advanced OCR, server-side rendering) that a browser can't match.
• Usually impose file-size caps, daily task limits, or a signup requirement on the free tier.
• Your document sits on someone else's server, which matters for contracts, IDs, medical records, or anything under a confidentiality obligation.

For routine tasks on sensitive files, local processing wins. Reach for a cloud tool only when you specifically need a capability the browser can't deliver — and check the retention policy before uploading.

The hidden costs of "free"

Free tiers differ in ways that only show up at export time. Before committing to a tool, check:

• Watermarks — some free converters stamp output unless you upgrade.
• File size or page caps — a "free" merge may refuse files over a certain size.
• Signup walls — requiring an account to download your own file.
• Export quality — compressed output that's visibly degraded, or converted text that comes out garbled.
• Task limits — a fixed number of operations per day.

BentoPDF's page states no signups, unlimited use, and $0 forever free, which is the pattern to look for if you want to avoid these traps. Treat any claim about pricing as specific to that tool and verify it on the site, since free tiers change.

A typical workflow, start to finish

1. Pick the narrowest tool for the job. For splitting, use a dedicated Split tool rather than a multi-tool — fewer settings to get wrong. BentoPDF's Split PDF extracts a page range into a new file; its PDF Multi Tool bundles merge, split, organize, delete, rotate, and extract in one interface.
2. Load the file. With a local tool, this reads the file into your browser — nothing is transmitted. Expect a short delay for large files as they're parsed.
3. Set the parameters. For a split, enter the page range. For a merge, set the file order. For compression, choose a quality level.
4. Export. The tool generates a new file for download. Keep the original untouched until you've verified the result.
5. Verify. Open the output and check page count, order, and that text is still selectable (not an image). This step catches most silent failures.

Common failures and what causes them

Merge produces a broken or reordered file. Usually a mismatch in page sizes or an encrypted source PDF. Check whether any input is password-protected before merging.

Compressed output is larger than the original. Compression re-encodes images; if the original was already optimized, you can end up bigger. Try a lower quality setting or skip compression.

Converted text is garbled. The source was likely a scanned image with no text layer, so the converter had nothing to extract. You need OCR, which not all free tools include.

Split output has the wrong pages. Page ranges are often 1-indexed and inclusive — confirm whether the tool counts from 0 and whether the end page is included.

Edits don't stick after saving. Some editors keep annotations in a separate layer. Use "flatten" or "remove annotations" if you need the changes baked into the page content.

How to choose, in one pass

• Sensitive document, routine task → local browser tool, no upload.
• Need OCR, advanced conversion, or collaboration → check a cloud tool's retention policy first.
• Want to avoid watermarks and caps → verify the free tier's export terms before you start.
• Handling very large files → local tools are fine but memory-bound; close other tabs.

The practical rule: match the tool to the task, keep sensitive files local, and always verify the export before deleting the original.

An online PDF editor lets you change a PDF in your browser, but "edit" covers several different jobs: rewriting existing text, annotating, redacting, filling forms, and reorganizing pages. The right tool depends on which one you need. For privacy, the key distinction is whether the file is processed locally on your device or uploaded to a server — BentoPDF, for example, states that all processing happens locally in the browser, with no uploads, no signup, and no file limits.

What "editing" actually means in a browser

These tasks are often lumped together, but they use different tools and produce different results.

BentoPDF lists Edit PDF Text as a tool that lets you click any paragraph and edit it in place with live reflow, fonts, and styling. Its PDF Editor handles annotation, highlighting, redaction, comments, shapes, images, and search — a different job from rewriting text. If your goal is to change wording, you need the first kind of tool; if you're reviewing, the second is enough.

Local processing vs. server upload

This is the decision that matters most for sensitive files.

• Local (in-browser) processing: the file stays on your device. BentoPDF describes itself as "privacy-first" and says all processing happens locally, with no uploads. It also states it works offline.
• Server-based processing: your file is transmitted to a remote service, processed there, and returned. You're relying on that provider's retention and security practices.

For a tax return, medical record, or signed contract, local processing removes the upload step entirely. For a public brochure, either works.

Check these limits before you commit

• File size caps — BentoPDF advertises "no file limits," but verify against your own largest file, since browser memory is the real constraint.
• Signup — BentoPDF states no signup is required. Many competitors gate features behind an account.
• Offline support — BentoPDF says it works offline, which is only possible if processing is genuinely local.
• Export quality — check that text stays selectable and images don't degrade after export.
• Cost — BentoPDF lists "$0 Forever Free" and asks for donations to stay free and open source. Treat pricing claims on any tool as something to confirm on the page itself.

A typical edit flow

1. Open the file — in BentoPDF, click a tool to open the file uploader, then select your PDF.
2. Pick the right tool — text editing for wording, the annotation editor for comments and redaction, the form filler for fields.
3. Make your changes — for text, click the paragraph and edit in place; reflow and styling update as you type.
4. Verify — scroll through the whole document. Check that fonts render, that redactions actually cover content, and that page order is correct.
5. Export a clean copy — save the result and reopen it to confirm the changes persisted.

Common problems and what causes them

• Text won't edit. Scanned PDFs are images, not text. You need OCR first, or you can only annotate on top.
• Fonts look wrong after editing. The original font may not be embedded or available in the browser. Expect substitution.
• Changes don't save. Usually an export step was skipped, or the browser tab was closed before the new file was written.
• Redaction isn't really redaction. A black box drawn as an annotation can often be removed or the text underneath copied. Use a tool that strips the content, such as BentoPDF's Remove Annotations for clearing comments and links, and confirm the exported file before sharing.
• Large files stall. Browser-based editing is limited by your device's memory, regardless of what the tool advertises.

Choosing between tools

If your priority is privacy for sensitive documents, favor a tool that processes locally and states it plainly — BentoPDF's "no uploads, works offline" claims fit that profile. If you need heavy text reflow on complex layouts, test the output carefully, since browser reflow can shift formatting. If you only need annotation or form filling, almost any editor will do, and the privacy question becomes less urgent for non-sensitive files.