What summarising a PDF actually means
A PDF is a layout file. It describes what text appears where, in what font, at what position on a page — but it doesn't preserve the document's logical structure the way HTML or Markdown does. A scientific paper PDF and a coffee-shop menu PDF look like the same kind of file to most software; they differ only in what's written and where.
Summarising a PDF means extracting the text content from the layout, feeding the text to a language model, and producing a condensed version. Two parts: extraction and summarisation. Both have failure modes. Both have edge cases. The combination produces useful summaries for a wide class of documents and useless summaries for a small class.
For an uploaded file, vust extracts the PDF text locally in your browser. The PDF file itself is not sent to the summary endpoint; only the extracted text is submitted for summarization.
URL mode is different: vust fetches the publicly accessible document or paper page from the address you provide. It cannot enter an institutional login or retrieve a password-protected file.
Why the file size cap is 15 MB
PDFs vary enormously in size, and file size does not equal useful text. The upload surface accepts files up to 15 MB and 50 pages per run.
Browser processing. Extraction happens inside the browser tab, so very large files can consume substantial memory and take longer to parse.
Useful text. A large scan may contain mostly images and no extractable text, while a smaller report can contain dense prose. The cap protects the interaction but does not guarantee that the document can be summarized.
For a larger document, extract the relevant chapter or page range first and summarize that smaller fragment. Section-level summaries are also easier to verify against the original.
What the summariser handles well
Several PDF categories produce reliably useful summaries.
Research papers. Standard academic PDFs (5-30 pages, abstract + introduction + body + conclusion + references) are the platform's strongest use case. The summariser captures the abstract's claims, the methodology, the key findings, and the limitations. For literature-review workflows, a paper-summary-per-paper is the right unit of intermediate organisation.
White papers and industry reports. Business-research documents (10-50 pages, executive summary + sections). The summariser extracts the headline findings without reading the entire body.
eBooks (text-based). Non-fiction eBooks distributed as PDF (rather than EPUB or MOBI). For chapters or whole books under the 15 MB cap, summarisation captures the high-level structure. Multi-hundred-page books usually need to be summarised chapter-by-chapter rather than whole.
Technical documentation. Software manuals, API references, user guides. The summariser captures the functional capabilities described without quoting the API signatures verbatim. Use the summary to decide whether to read the full doc.
Lecture slides exported as PDF. Presentation slides converted to PDF retain the bullet-point text that was on each slide. The summariser turns slide bullets into a coherent paragraph or bullet summary.
Business reports and meeting minutes. Internal documents (5-20 pages) where the structure is informal but the text is rich.
What the summariser cannot do well
Several PDF categories defeat the extract-then-summarise approach.
Scanned image-only PDFs without OCR. A file made only of page images has no text layer for the browser to extract. Run OCR first, then submit the searchable PDF or extracted text.
Encrypted or password-protected PDFs. The browser extractor cannot open them. Remove the password only if you are authorized to do so, then retry.
PDFs where the visual layout is the message. Comic books, infographics, complex diagrams, brochures with heavy visual design. The text is fragments and labels; the summary captures fragments and labels. Look at the original.
Multi-column layouts with running headers. Newspaper PDFs and journals with two-column layouts and running headers / footers extract in non-linear order — a sentence might come from column 2 of page 5 in the middle of column 1 of page 4. The summariser tries to reorder coherently but sometimes produces disjointed summaries for these layouts.
Tables and figures. A PDF with a key chart or data table loses the chart entirely (charts are image objects, not extractable text). Tables sometimes extract as misaligned columns. For PDFs where a table or figure is the centerpiece, the summary describes only the surrounding prose.
Equations and mathematical notation. PDFs with LaTeX-rendered equations export the equations as image objects. Extraction returns nothing for those equations. Summary of a math-heavy paper captures the prose around the equations but not the equations themselves.
Very long text. A single-pass summary may not cover every section. Split the document and keep section headings with each excerpt so omissions are visible.
Common gotchas
The first-page title may not match the document title. Some PDFs have a cover page (logo, blank, copyright notice) before the actual title page. The extracted "title" comes from the first non-empty text block on page 1, which sometimes is a copyright disclaimer rather than the actual document name.
Page numbers, headers, and footers contaminate the text. A PDF with "Confidential — page 5 of 40" repeated on every page injects that string into the extracted text many times. The summariser usually skips the boilerplate but occasionally surfaces it as a bullet point. Re-run if the summary's first bullet is page-header noise.
Hyperlinks in the PDF appear as raw URLs. A clickable "see our website" link in the PDF extracts as "see our website" followed by a literal URL. The summariser preserves the URL as a fact when the URL is meaningful.
Footnote markers can confuse the prose flow. A sentence with three footnote references might extract as "the data shows X 12 13 14, suggesting Y." Where 12 13 14 are footnote numbers. The summary usually elides these but some footnote-heavy academic papers produce slightly fragmented summaries.
Embedded fonts can break extraction. Some PDFs decode into question marks, boxes, or out-of-order text. Re-export from the source application or use a different text extractor before summarizing.
Non-Latin scripts depend on the embedded text layer. If copied text is already garbled in a PDF viewer, the summary will inherit the same problem.
When a different tool fits better
For OCR-needed PDFs, run OCR first. Adobe Acrobat Pro has a built-in OCR pass (Tools → Scan & OCR → Recognise Text). Free alternatives include tesseract on the command line and Google Drive's OCR (upload a PDF, then "Open with Google Docs" runs OCR).
For PDFs with critical tables and charts, use a layout-preserving extraction tool. pdfplumber (Python) and Camelot extract tables. For chart data, manually re-create the chart from the source data rather than relying on extraction.
For a long document, summarize chapter by chapter or section by section. Keep the section title and page range beside every result so the final synthesis can be checked against the source.
For presentations where the visual design carries meaning (sales decks, pitch decks), the PDF text extraction misses what the slides communicate visually. Watch the recording or review the deck visually.
If the output language or source script does not render cleanly, extract a short sample first. Translate the text only after confirming that names, numbers, and headings survived extraction.
A workflow for using PDF summaries
For research workflows where you need to triage a stack of papers:
- Upload each paper, run a bullet summary, save the bullets alongside the citation.
- Read the summaries to decide which papers warrant a full read.
- For papers that pass the triage, read in full with the summary as a navigation aid.
For business workflows where you receive a long document and need the headline points:
- Upload the PDF, run a key-takeaways summary (3-5 takeaways).
- Compare the takeaways to what the sender said the document was about.
- If the takeaways and the framing align, you're done — the document confirms the framing.
- If they diverge, read the relevant sections of the PDF in full.
For learning workflows (textbook chapters, technical guides):
- Summarise the chapter as bullets first.
- Use the bullets as a study outline.
- Read the chapter in full with the outline guiding your attention.
- Save the bullet summary as your study notes.
The summary is a navigation tool and a recall aid, not a replacement for the source document. For PDFs that matter, use the summary to scope the work before reading the original.