getmarkdown.com

Use GetMarkdown's free browser converter for ordinary text-based PDFs up to 10 MB each, 8 files per batch — no account, no daily quota, and the file contents stay in your browser. Switch to Pro (server-side, paid per page with credits) when the PDF has complex tables, multi-column layouts, or scanned pages that need OCR, or when you need RAG-ready Markdown plus structured JSON. The deciding question is simple: if you can select and copy the text in a PDF viewer, the free path will almost always work; if you can't, plan on Pro.

Free conversion in the browser: steps and limits

1. Check the file first. Open the PDF and try selecting a paragraph. Selectable text means a text layer exists — the free converter can extract it. No selection means it's a scan or image-only export.
2. Confirm size and count. Free conversions are capped at 10 MB per file and 8 files per batch. Larger files or bigger batches aren't blocked forever — just split them and start another batch, since there's no daily quota.
3. Add the files. On the GetMarkdown page, select up to 8 local files by clicking or dragging and dropping. The counter shows how many are selected (e.g., "0 / 8 files selected").
4. Convert. Click Convert to Markdown. Processing runs locally via WebAssembly, so the selected file contents are not uploaded to GetMarkdown.
5. Download and inspect. Open the resulting .md file and check headings, paragraph breaks, lists, and any tables before you feed it to an LLM, a RAG pipeline, or a knowledge base.

The free tier is genuinely unlimited in the sense that you can repeat batches as often as you like — the 8-file/10 MB caps apply per batch, not per day.

When free conversion isn't enough

Free local conversion is built for text extraction, not layout reconstruction. Three situations reliably push you to Pro:

• Complex tables. Merged cells, multi-row headers, and tables that span pages tend to come out as jumbled pipe tables or loose text.
• Scanned pages. No text layer means nothing to extract locally; OCR is required.
• RAG-ready output. If you need structured Markdown and JSON with preserved document structure, that's the Pro output format.

Pro is a separate, paid server-side option, and the page states it is clearly labeled before upload — so you always know when a file is leaving your browser. It handles PDFs up to 25 MB and 500 pages, requires a free account, and is priced in credits: one credit per text page, two per scanned page, with the quote shown before anything is charged. It returns a ZIP containing Markdown and structured JSON. Credit packs start at $9 for 500 credits.

Free vs. Pro at a glance

Cleaning up the Markdown before it reaches an LLM

Conversion is half the job; a quick pass makes the output far more usable as context:

• Fix heading levels. Confirm the document's real hierarchy (H1 for the title, H2 for sections) rather than trusting whatever the converter inferred.
• Rebuild broken tables. Re-align pipe tables by hand or drop them into a table block your editor understands; malformed tables confuse retrieval more than plain text does.
• Strip repeated headers and footers. Page numbers and running titles often survive extraction and add noise to every chunk.
• Check list and code formatting. Nested lists and code blocks are the most common casualties of PDF extraction.
• Chunk with structure in mind. For RAG, split on headings rather than fixed character counts so each chunk stays semantically whole.

Troubleshooting common failures

The file won't convert or the browser stalls. Check the size against the 10 MB cap first. Very large or heavily image-laden PDFs can strain browser memory even under the limit — split the PDF into smaller page ranges and convert in separate batches.

The output is empty or nearly empty. This is the signature of a scanned PDF with no text layer. Verify by trying to select text in a viewer; if nothing selects, the free converter has nothing to extract and Pro's OCR is the right tool.

Tables come out scrambled. Free conversion doesn't reconstruct complex layouts. For anything with merged cells or multi-page tables, use Pro, or convert the table separately and paste it in as a clean Markdown table.

Images are missing. Image packaging into a ZIP with relative references is described for Word and PowerPoint files, not PDFs — don't expect embedded images from a free PDF conversion. If figures matter, extract them from the PDF separately and link them in.

You need JSON, not just Markdown. That's a Pro-only output; the free tier returns Markdown only.

Other formats on the same page

If your source isn't a PDF, the same free converter accepts Word (.docx), PowerPoint (.pptx), Excel (.xlsx), HTML (.html/.htm), plain text (.txt), images (.jpg/.jpeg/.png), and audio (.mp3/.wav). For Word and PowerPoint files, detected images can be packaged in a ZIP alongside the Markdown with relative image references — a useful detail when you're assembling a knowledge base from mixed sources.

To convert a Word .docx file to Markdown for free, open GetMarkdown in a browser, select up to 8 local files (10 MB each), and click Convert to Markdown. The conversion runs locally in your browser via WebAssembly, so file contents are not uploaded. This works for standard .docx files; legacy .doc is not in the supported format list, so save it as .docx first. After conversion, review headings, lists, tables, and links, because Word styling does not always map cleanly to Markdown.

Before you convert: confirm the file is supported

GetMarkdown lists Word (.docx) under documents. The supported formats on the page are:

If your file is an older .doc, it is not listed. Open it in Word or another editor and save a copy as .docx before converting. Also check the file size: free browser conversions are limited to 10 MB per file and 8 files per batch.

Step-by-step: convert DOCX to Markdown in the browser

1. Open the converter. Go to GetMarkdown and find the Select Your Files area.
2. Add your file. Click to select or drag and drop your .docx. The counter shows how many of the 8 slots you have used (for example, 1 /8 files selected).
3. Start conversion. Click Convert to Markdown. Processing happens locally in your browser.
4. Download the result. Save the Markdown file. If your document contains images, expect a ZIP archive (see the next section).
5. Verify the output. Open the .md file in a plain-text or Markdown editor and check the structure before using it in an LLM pipeline, knowledge base, or tool such as Obsidian, Notion, or GitHub.

If you have more than 8 files, convert them in batches; the page states there is no daily quota, so you can start another batch whenever you like.

How images in Word documents are handled

When images are detected in Word and PowerPoint files, GetMarkdown can package them in a ZIP archive alongside the Markdown file and use relative image references. In practice:

• Extract the ZIP to a folder.
• Keep the .md file and the image folder together so the relative paths resolve.
• If you move the Markdown file elsewhere, move the images too, or update the paths.

This matters for RAG pipelines and static site generators, where broken image links silently degrade output quality.

Check and fix the Markdown after conversion

Word formatting is visual; Markdown is structural. Expect to review these areas:

• Headings: Word "Heading 1/2/3" styles usually become #, ##, ###. Direct formatting (bold, larger font) may not.
• Lists: Nested lists can lose indentation. Confirm each level uses consistent spacing.
• Tables: Simple tables usually survive; merged cells and complex layouts often do not. Rebuild those manually.
• Links: Confirm hyperlinks kept their URLs and did not collapse to plain text.
• Emphasis: Bold and italic generally carry over; check inline code and strikethrough.

A quick pass with a Markdown linter or preview pane catches most structural issues before the file reaches an AI agent or knowledge base.

Troubleshooting common failures

The file will not convert

• Wrong extension: .doc is not supported. Save as .docx.
• File too large: Free conversions cap each file at 10 MB. Reduce embedded images or split the document.
• Too many files: The batch limit is 8. Convert in smaller groups.

Images are missing

Images arrive in a ZIP with relative references. If you downloaded only the .md file, the images will not appear. Extract the ZIP and keep the files together.

Tables or layout look wrong

Complex tables, text boxes, and multi-column layouts are the usual culprits. Rebuild those sections by hand in Markdown. For PDFs with hard tables or scanned pages, GetMarkdown offers a separate Pro option: server-side processing up to 25 MB and 500 pages per PDF, requiring a free account and credits (one per text page, two per scanned page, with a quote shown before charging; credit packs start at $9 for 500 credits). That option is for PDFs, not Word files.

Output is messy for LLM use

Strip leftover Word artifacts (empty lines, stray characters) and normalize heading levels. Structured Markdown is what the page promises for RAG pipelines, LLM context windows, and agent workflows, but a short cleanup pass improves retrieval quality.

When the free browser route is the right choice

Use the free browser conversion when your .docx is under 10 MB, you have 8 or fewer files, and the document uses standard headings, lists, and simple tables. It requires no sign-up, and file contents stay in your browser. If your source is a complex or scanned PDF rather than Word, the Pro server-side option is the labeled paid path; for .docx, the browser converter is the documented route.

You can convert PDF, Word, PowerPoint, Excel, HTML, plain text, image, and audio files to Markdown directly in a browser with GetMarkdown. Free conversions run locally, accept up to 8 files per batch at 10 MB each, and require no account. If you have complex or scanned PDFs with tables that need stronger layout or OCR handling, the paid Pro option processes them server-side. The steps below cover the free path first, then the Pro path and its limits.

Supported formats and what to expect

For Word and PowerPoint files that contain images, GetMarkdown can package the images in a ZIP archive alongside the Markdown file and reference them with relative paths. That keeps the document portable when you move it into an editor or repository.

Convert files in the browser (free, private)

1. Open the converter and locate the file selection area, labeled "Select Your Files."
2. Add up to 8 local files by clicking to select or dragging and dropping. The counter shows how many of the 8 slots you have used.
3. Start the conversion with the "Convert to Markdown" action.
4. Download the result. For Word and PowerPoint files with images, expect a ZIP containing the Markdown file and its image folder.

Expected result: clean, structured Markdown you can paste into Obsidian, Notion, GitHub, or an LLM pipeline.

Verify it worked: open the Markdown file and check that headings, lists, and tables survived. For image-bearing documents, confirm the relative image paths resolve after you unzip the archive.

Common snags:

• A file over 10 MB is rejected. Split or compress it first.
• More than 8 files in one batch is blocked. Convert in additional batches; there is no daily quota.
• Scanned PDFs may produce thin or garbled text in the free path because there is no OCR step.

Privacy on the free tier

Free conversions use local WebAssembly processing in your browser, so selected file contents are not uploaded to GetMarkdown. This matters if you are converting contracts, internal notes, or anything you would not paste into a random web service. The trade-off is that very large or layout-heavy files are more likely to hit the 10 MB ceiling or lose table structure.

When the free conversion is not enough

Choose the Pro PDF path when your source is a complex or scanned PDF and you need structured Markdown plus JSON output, for example a financial report with multi-column tables or a scanned invoice you want to feed into a RAG pipeline.

What Pro changes:

• Server-side processing for PDFs, clearly labeled before upload, so file contents do leave your browser at that point.
• Larger limits: up to 25 MB and 500 pages per PDF.
• Credits, not a flat fee: one credit per text page, two per scanned page, with the quote shown before anything is charged.
• Account required: Pro needs a free account.
• Output: a ZIP containing Markdown and structured JSON.
• Entry price: credit packs start at $9 for 500 credits.

A rough cost check: a 100-page text PDF costs about 100 credits; a 100-page scanned PDF costs about 200. At the entry pack, that is several documents before you need another pack.

Choosing between the two paths

Using the Markdown downstream

The output is structured Markdown intended for AI agents, RAG pipelines, knowledge bases, and Markdown editors. Practical checks before you rely on it:

• For RAG or LLM context: skim for broken tables and stray characters, especially from PDFs. Clean chunks retrieve better than messy ones.
• For note apps: relative image references work in Obsidian and GitHub-style repositories; some tools need images re-linked after import.
• For version control: commit the Markdown and its image folder together so diffs stay readable.

If a converted file looks wrong, the fastest diagnosis is to compare the source layout against the Markdown: missing tables usually mean a PDF that needs Pro, while missing images usually mean the ZIP was not extracted alongside the Markdown file.

GetMarkdown converts PowerPoint (.pptx) files to Markdown directly in your browser, free and without an account. Select up to 8 files per batch (10 MB each), click Convert to Markdown, and download the result. Images found in the slides are packaged in a ZIP alongside the Markdown file with relative image references. This guide covers the exact steps, how to check the output, and what to do when a conversion fails or content goes missing.

Before You Start: Supported Format and Free Limits

The free browser converter accepts .pptx files. Two limits apply per batch:

• 8 files maximum per batch
• 10 MB maximum per file

There is no sign-up and no daily quota — once a batch finishes, you can start another immediately. Conversions run locally in your browser using WebAssembly, so the contents of your selected files are not uploaded to GetMarkdown.

If your deck exceeds 10 MB, split it into smaller files before converting. If you have more than 8 decks, convert them in multiple batches.

Step-by-Step: Convert a PowerPoint File in the Browser

1. Open the converter on getmarkdown.com and locate the "Select Your Files" area.
2. Add your file(s). Click to select or drag and drop up to 8 .pptx files. The counter shows how many files are selected (e.g., "0 /8 files selected").
3. Click "Convert to Markdown." Conversion happens locally in your browser.
4. Download the output. You receive a Markdown file. If images were detected in the slides, you also get a ZIP archive containing the images, with the Markdown using relative image references to them.
5. Keep the Markdown and image folder together. Because references are relative, the Markdown will only display images correctly if the image files sit in the expected location relative to the .md file.

Expected result: a .md file whose slide titles, bullet lists, and text content are represented in Markdown syntax, plus an image archive when applicable.

How Images in Slides Are Handled

When GetMarkdown detects images in a PowerPoint file, it packages them in a ZIP archive alongside the Markdown file and writes relative image references into the Markdown. This means:

• Extract the ZIP before viewing or publishing the Markdown.
• Preserve the folder structure the archive provides so the relative paths resolve.
• If you move the .md file into another tool (e.g., a knowledge base or Git repo), copy the image files along with it and keep the same relative layout.

Decorative elements, charts, and SmartArt may not survive as clean Markdown — check these manually after conversion.

Checking the Output Quality

Open the .md file in a plain-text or Markdown editor and verify:

If headings are flat or lists are broken, fix them with a quick pass in your editor — the text content is usually intact even when structure needs adjustment.

Troubleshooting Common Problems

The file won't select or convert. Confirm it is a .pptx file (not .ppt) and under 10 MB. Legacy .ppt files are not in the supported list — save them as .pptx in PowerPoint first.

The batch won't accept more files. You've hit the 8-file limit. Convert the current batch, then start a new one.

Images are missing or broken in the Markdown. Extract the ZIP archive and keep the image folder next to the .md file with the same relative paths. If no ZIP was produced, the deck may contain no detectable embedded images, or the images are drawn as shapes/charts that aren't exported as image files.

Text is missing or garbled. Text inside images, scanned slides, or unusual embedded objects won't be read as text. Copy that content manually. Very large or heavily designed decks can also produce messy structure — a manual cleanup pass is usually faster than re-converting.

The browser tab stalls on a large deck. The 10 MB per-file limit exists for browser stability. Split large presentations into sections and convert each separately.

When to Use Pro Instead

The free browser converter is the right choice for standard text-and-image decks within the size limits. GetMarkdown's Pro option is a separate, paid server-side service for PDFs that need stronger table, layout, or OCR handling (up to 25 MB and 500 pages per PDF). It requires a free account, uses credits (one per text page, two per scanned page, with the quote shown before charging), and returns a ZIP with Markdown and structured JSON. Credit packs start at $9 for 500 credits.

For PowerPoint specifically, the practical path is: convert the .pptx free in the browser, and if you later need the deck as a PDF with complex tables or scanned pages, consider Pro for that PDF step.

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.