Measured on real files

How to Convert PDF to PowerPoint Without Broken Slides

We converted five test files — an A4 report, a ruled table, a chart-only page, a scan and a poster — in the AFFLIGO converter, then measured the PPTX each one produced. Here are the exact rules it follows, the numbers behind them, and the two-minute fixes when a slide arrives wrong.

180 DPI image slides 77 DPI editable 0 uploads
By Karan Kumar Updated November 3, 2026 20 min read
Quick Summary

01Start Here: Three Questions, Thirty Seconds

Most bad conversions are the wrong slide mode for the source file, not a broken converter. Answer these three before you drop the PDF.

Every number on this page comes from running the AFFLIGO PDF to PowerPoint converter on three test files and reading the exported PPTX directly: a 2-page A4 report with a 5x6 ruled table, a single chart-only page carrying 320 vector operations, and a text-light scan. Slide size was read from presentation.xml, resolution from the embedded page JPEG, and table count from the slide XML.

QuestionWhat it tells youThen do this
Can you select the text?Drag across a paragraph. If nothing highlights, the page is a picture, not text.Run OCR first. Editable mode cannot invent text that is not in the file.
What shape is the page?A4 and Letter are portrait. A deck exported from widescreen slides is 13.33 x 7.5 in.Expect portrait slides from A4. Need widescreen? Export the source as a 16:9 PDF first.
Projector or print?Projection hides soft edges. Paper, zoom and 4K displays expose them.Use Image mode (180 DPI) for print. Editable is for decks you still have to change.
The short version

Text-based PDF that needs editing: Editable text. Scanned PDF, or a deck you will only present: Image slides. Printing, or projecting at 1080p with no edits planned: Image slides. Everything else is a detail, and the details are below.

02What Survives Conversion, Measured

One PDF page still becomes one slide. What lands on that slide is where the two modes part company.

Below is the exported file, not the marketing promise. Each row was checked in the PPTX the converter produced for the 2-page A4 test report, and the counts are the counts the file actually contains.

ElementImage slidesEditable text
Page appearanceExact. The page is rendered, not rebuilt.Approximate. Page image plus repositioned text boxes.
Selectable textNoYes. 32 text boxes on the long page of our A4 test, 5 on the short one.
Tables with drawn bordersNo, part of the pictureYes. A 5x6 ruled grid produced 1 native PowerPoint table.
Tables drawn with fills onlyNo, part of the pictureCells become text boxes. No table shape, no cell borders to drag.
HyperlinksNoNo. The exported slide contained 0 link elements.
FontsRendered exactly as drawnDeck theme font, Calibri by default. The original font is not carried.
Photos and chartsInside the page imageInside the page image, not separate objects
Speaker notesNoneNone. PDF has no notes to carry.
Transitions and animationNoneNone. Add them after conversion.
Screen-reader textNoneText boxes only, and no alt text on the page image.
Page image resolution (A4)1489 x 2104 px, 180 DPI637 x 900 px, 77 DPI

The pattern is simple: Editable mode buys you text and ruled tables, and pays for them in fidelity. The page background drops from 180 DPI to roughly 77 DPI because the image now sits behind live text, and anything that needs a real PowerPoint object — a chart, a photo, a logo — stays baked into that background either way.

03Why a Page Came Out as a Picture

The converter does not guess. It runs three tests per page, in this order, and the first one that matches decides the page.

01

No characters at all

If the page yields zero text characters, it is a scan. Nothing can be rebuilt as text, so the page becomes an image slide in either mode, and the report names the slide. There is no setting that changes this.

02

Vector-heavy, text-poor

If the page has no detected table, more than 250 vector operations (rectangles, line segments and fills combined), and fewer than 150 characters, it is treated as a complex graphic. Rebuilding that as shapes produces a mess, so the page stays an image and the tool says so.

03

Everything else

The page is rebuilt with text boxes, and with native tables where a table was detected. This is the common case: a normal report or contract page lands here even when it has a chart or a logo on it.

Two details explain most "why did this one go weird" questions. A page that carries a detected table is never treated as complex, because the table proves the page has structure worth rebuilding. And the vector count is not a quality score — it is a shape count, so a detailed org chart with a paragraph of labels can clear 250 operations and still convert as editable while a sparse diagram with forty words does not. Order matters as well: our scan-only test page carried 221 vector operations and still classified as a scan, because the zero-character test runs first.

Test pageCharactersVector opsTableVerdict
Chart-only page8320NoneImage slide
A4 report, page 147165YesEditable
A4 report, page 22570NoneEditable
Scanned page0221NoneImage slide
What you can actually change

You cannot lower the threshold, but you can change the input. Split the deck so chart pages are separate files, add a text caption to a diagram page before exporting the PDF, or accept the image slide and put the editable commentary in the speaker notes instead. For a page you genuinely need to edit, PDF to Word keeps text editable without rebuilding a slide layout.

04Real Tables vs Text Boxes: The Border Rule

A table survives as a table only if the PDF drew it with lines. This is the single biggest cause of "the conversion lost my table".

Table detection works on the PDF's vector drawing data: it looks for ruling rectangles and line segments, groups them into a lattice, then reads the text inside each cell. When those lines exist, the cells are masked out of the page image and re-emitted as a native PowerPoint table you can restyle, resize and add rows to.

When the "borders" are actually background fills, alternating row colours, or nothing at all, there is no lattice to read. The extractor falls back to clustering text by position, and the cells arrive as ordinary text boxes. They still sit in the right place, so the slide looks correct, but PowerPoint does not see a table.

How the PDF draws the tableWhat the deck getsMeasured
Ruled grid (Word, LibreOffice, Excel exports)One native PowerPoint table, rebuilt from the cell lattice5x6 grid: 1 table, 31 text runs
Fill-only or borderless (browser print, Canva, many design tools)Positioned text boxes, no table shape5-row table: 0 tables, 32 text boxes
Check before you convert

Zoom to 400% on a table border. A ruling line stays a sharp one-pixel line and its colour is separate from the cell fill. A borderless table has no line at all, only a colour change. If it is borderless, expect text boxes.

Two practical limits sit on top of this. The converter rebuilds up to 8 tables per page; the ninth and beyond stay inside the page image. And clustered tables are approximate: on our browser-printed test the detector returned a 5-row grid padded to 8 rows, with adjacent heading text pulled into the first cell. That is why a fill-only table is better rebuilt as a real table in PowerPoint than trusted as-is.

If the deck is going to be edited heavily, the cleaner route is PDF to Excel for the data, then paste the sheet into PowerPoint as a table. For the visual version you present, use Image mode and leave the table where it belongs — inside the page.

05A4 vs 16:9: Why Your Deck Is Portrait

The deck inherits the page's shape. A4 in, A4 out — and that surprises everyone who expected widescreen.

Slide size is copied from the PDF's page box, in inches, capped at 13.33 in on the long edge. Our A4 test page measured 595 x 842 pt, and the exported deck came out at 8.26 x 11.69 in — a portrait slide, ratio 0.71. Nothing is stretched or letterboxed in the file; it is simply a page-shaped deck. A 16:9 PDF, the kind PowerPoint itself exports, arrives at 13.33 x 7.5 in instead.

On a projector the difference is visible immediately: a portrait deck sits in the middle of a 16:9 frame with wide bars on both sides, and every slide reads smaller than it would in a widescreen deck. On a phone or a printed handout, the portrait deck usually wins.

Source pageSlide size you getShape
A4 (595 x 842 pt)8.26 x 11.69 inPortrait
US Letter (612 x 792 pt)8.5 x 11 inPortrait
16:9 deck PDF (960 x 540 pt)13.33 x 7.5 inWidescreen
Anything above 13.33 inCapped at 13.33 in per axisSqueezed, not proportional

The cap is applied to each axis separately, not to the aspect ratio. That is invisible for A4 and 16:9, but a large-format page distorts: our 20 x 40 in test poster came out as a 13.33 x 13.33 in square slide with the page image stretched across it. If you convert posters or plotter output, resample the page to a normal size before conversion.

01

Converting to widescreen after the fact

Open the deck, go to Design → Slide Size → Widescreen. PowerPoint asks you to choose. Scale to Fit enlarges every object proportionally, which keeps the layout intact but stretches the 77 DPI page image across a wider canvas, so it loses sharpness. Ensure Fit keeps objects at their size and leaves empty bands, which looks worse on a projector.

02

Better: start from a widescreen PDF

In the source PowerPoint, set Design → Slide Size → Widescreen before exporting, then File → Save As → PDF. Convert that file and the slides arrive at 13.33 x 7.5 in with the text already laid out for widescreen. If the source was a Word document, print it to PDF with a 13.33 x 7.5 in page size instead of A4.

Rule of thumb

If the deck will be projected, convert a widescreen PDF. If it will be read on paper or a phone, keep the A4 shape — resizing after conversion costs resolution, and the portrait page was the more faithful copy.

06Sharpness: 180 DPI vs 77 DPI

Same page, same converter, two very different pixel counts. This is the trade nobody documents.

Image mode renders the page at up to 2.5x and gives you a 180 DPI background. Editable mode renders the page behind the live text at a maximum of 900 px on the long edge — roughly 77 DPI on A4 — because the text, not the image, is supposed to carry the content. Both were measured on the same 2-page A4 file.

ModePage image (A4)Resolution2-page file
Image slides1489 x 2104 px180 DPI239 KB
Editable text637 x 900 px77 DPI126 KB

That second row also corrects a common assumption: on this file, Editable produced the smaller deck, not the larger one. The text is a few kilobytes; the background is what dominates file size, and editable mode's background is less than half the pixel count of image mode's.

What the numbers mean in practice: a 1080p projector shows a full-screen slide at about 1920 x 1080. A 13.33 in widescreen slide whose background is 960 px wide gets upscaled roughly 2x, which is visible on fine text and hairlines at the back of a room. A portrait A4 slide at 900 px tall is upscaled about 1.2x on the same projector, which is far less noticeable. For print, 180 DPI is acceptable for office documents and short of the 300 DPI usually asked for photo-quality output.

What you will do with the deckModeWhy
Project at 1080p, no editsImage180 DPI background, nothing to upscale badly
Edit text, then projectEditableLive text stays crisp; the background only shows through in gaps
Print handoutsImage180 DPI is the best this route offers — or print the original PDF
Archive the contentEditableText survives copy, search and reflow
If print quality is the requirement

A converted deck is not a print pipeline. Print the original PDF, or place the pages as high-resolution images in PowerPoint yourself — the converter's job is to make a presentable deck, and 180 DPI is the ceiling it targets.

07The 90-Second Slide Rescue

Four defects account for almost every "the conversion ruined it" deck. Each has a one-command fix.

01

Text is in the wrong font — 20 seconds

Home → Replace → Replace Fonts, choose the substitute that arrived, choose your brand font, click Replace. This rewrites every run in the deck at once. Do not select-all-and-set-font: that also hits text boxes you wanted left alone.

02

Text spills out of its box — 30 seconds

Select the box, then Shape Format → Text Options → Text Box → Shrink text on overflow. Set it once and copy the formatting to the other boxes with the Format Painter. The alternative is nudging each box, which takes ten times as long.

03

Columns are ragged — 60 seconds

Select the boxes in one column, then Shape Format → Align → Align Left, then Distribute Vertically. If you cannot click a box because another sits on top, open Home → Select → Selection Pane and pick it by name.

04

The deck is portrait — 10 seconds

Design → Slide Size → Widescreen → Scale to Fit. Everything scales together, so alignment survives; the page image loses sharpness because it is being enlarged. See the slide-size section for when to reconvert instead.

Stop rule

If more than a third of the slides need repairs, the mode was wrong. Reconvert in Image mode and present the pages as they are — that is faster than fixing a deck that was never meant to be editable.

08Six Sources, Six Right Answers

The file in front of you decides the mode more than your preference does. Match the source, then stop second-guessing.

Source PDFHow to spot itModeWhat to expect
Word or InDesign reportCrisp one-pixel table borders, selectable textEditableNative table plus text boxes. Fix fonts once, done.
Scanned contractNothing highlights when you drag; page looks like a photoOCR, then EditableText layer over a 77 DPI background. Expect 10 minutes of cleanup.
Canva or browser printColoured blocks, no border lines, drop shadowsImagePixel-perfect pages, nothing editable. That is the correct trade.
Excel printoutWide ruled grid, small type, repeated header rowEditableTable rebuild, up to 8 per page. Long sheets may split awkwardly.
PPT saved as PDF13.33 x 7.5 in page, one idea per pageImage to present, Editable to changeReal 16:9 slides. Image mode gives 180 DPI, editable 72 DPI.
Two-column paperTwo text columns, figures and captions inlineEditableEach column becomes its own stack of text boxes. Figures stay baked.

Two rules cover the leftovers. If the PDF has pages you do not need, extract them first with Split PDF — there is no page-range selector in the converter, and a 100-page deck is slower to build and harder to repair. If the PDF needs a password to open, the converter asks for it in the tab and unlocks it before rendering; fall back to Remove PDF Password only if the prompt does not appear.

09Scanned PDFs and OCR: When It Pays Off

A scan has no text to rebuild, so the converter can only hand you pictures of pages. OCR is what changes that — sometimes.

A scanned PDF stores each page as one large image. Editable mode still runs, still reports the pages, and still returns image slides, because there are no characters to place. Running OCR first adds a hidden text layer over those images, which is what makes text selectable afterwards.

01

OCR the scan

Send the file to OCR PDF, pick the document language, and run it. The output is a new PDF: same pages, plus a searchable text layer.

02

Check the text before converting

Open the OCR output and try to select a sentence. If the words come out scrambled, the scan was too poor and a converted deck will carry the same errors. Fix or rescan first — converting does not improve recognition.

03

Convert in Editable mode

Now the pages have text, so editable mode has something to place. The background stays the scanned image at about 77 DPI, so the slide looks identical while the text on top is real.

When OCR is not worth it

Handwriting, phone photos taken at an angle, fax-quality copies, stamps and signatures all defeat recognition. If the page exists to be shown and not edited, skip OCR and use Image mode — you get the identical visual result in a fraction of the time.

10Verify the Privacy Claim in 20 Seconds

"Nothing is uploaded" is a promise. The Network tab turns it into something you can check yourself.

Conversion runs on PDF.js and PptxGenJS inside your tab, so the file has no route off the device. That is easy to verify and you should verify it before putting a confidential document into any converter, including this one.

01

Open the Network tab

Load the converter, press F12, and switch to Network. Leave it open and unfiltered so nothing can hide behind a filter.

02

Clear, then convert

Click the clear button, then drop your PDF and run the conversion. Watch the request list while it works. A page render is CPU-heavy and network-quiet — that contrast is the whole proof.

03

Read the list

You will see the page's own assets: scripts, fonts, the PDF worker. What you will not see is a request whose size matches your file, or a POST carrying its bytes. That request is what "uploaded" would look like.

Cloud import is the one case where data moves, and it moves in the other direction: with Google Drive or Dropbox you authorise read access and the file is fetched into the tab. AFFLIGO requests the narrow drive.file scope, which reaches only files you pick in the picker — not your whole Drive. Nothing is written back and no token is kept after the tab closes.

The honest limit

Because nothing is stored, nothing can be recovered. Close the tab before downloading and the deck is gone — there is no server copy, no history, and no support route to bring it back. Save the file before you close the browser.

11Accessibility: The Invisible Deck

An image slide is a blank page to a screen reader. If the deck has to meet an accessibility standard, that changes the mode you pick.

Image mode puts the entire page into one picture. Visually it is perfect; semantically it is empty. A screen reader announces a graphic with no description and no text, so a 40-slide image deck can be completely unreadable while looking flawless in the slide sorter. Editable mode helps — the text boxes are real text — but the page background is still an undescribed picture, and the reading order follows the order boxes were added, not the order a person would read.

The relevant standard is WCAG 2.2 success criterion 1.1.1, which requires a text alternative for non-text content. Public-sector and many enterprise decks are also covered by Section 508 in the US and the European Accessibility Act, which applies from June 2025.

01

Pick Editable for text-heavy pages

Text boxes are exposed to assistive technology. An image-only deck cannot be repaired by adding alt text to 40 pages — that is 40 hand-written descriptions, and most teams give up halfway.

02

Describe the page image

Right-click the background picture and choose Edit Alt Text. One sentence is enough: what the page shows, not every word on it. Mark decorative pages as decorative so the checker stops flagging them.

03

Put the content in the notes

Speaker notes are read by screen readers and exported as a transcript. If the deck is a converted report, the notes are the cheapest way to make the argument readable without touching the layout.

04

Run the checker

Review → Check Accessibility lists missing alt text, merged-cell problems and duplicate slide titles. Fix the errors it reports before the deck leaves your machine.

Do not overclaim

A converted deck is a starting point, not a compliant document. Editable mode exposes text; it does not fix reading order, and it does not label the background. Budget one pass with the accessibility checker for any deck that has to be published.

12Round-Tripping Into Google Slides and Keynote

Converting to PPTX is not the last hop. What happens next depends on which app opens the file.

The common mistake is uploading the PDF straight into Google Drive and using "Open with Google Slides". That is not a conversion: Drive usually turns each PDF page into an image on a slide, so you end up with the same non-editable result you were trying to escape. Convert to PPTX first, then import the deck.

AppTablesFontsLayout risk
Google SlidesNative tables import as Google tablesReplaced with Google fontsCell borders and fills can drop; portrait decks stay portrait
KeynoteConverts to Keynote tablesSubstituted if not installedTheme may override colours and spacing
LibreOfficeFull fidelityDepends on installed fontsLowest risk of the three

The import path matters. In Google Slides use File → Open → Upload and pick the .pptx, rather than dragging it into Drive and double-clicking. Uploading keeps the deck as a Drive file you can re-import; converting on open can silently flatten objects.

Best of both

Convert to PPTX, fix fonts and slide size in PowerPoint where the controls are precise, then import into Google Slides for comments and real-time editing. Doing it in the other order means repairing the deck twice.

13Desktop Routes: PowerPoint's Own Import and Acrobat

Two desktop apps will attempt this same job without any converter. Neither is wrong — they fail in different places, and knowing which one you are relying on explains most surprise results.

This is also the honest answer to how to open a PDF in PowerPoint without converting it first. PowerPoint handles it directly: File → Open, switch the file-type filter to PDF, and it builds an editable presentation from the pages. Newer versions show a conversion dialog first, then rebuild each page from text runs and shapes instead of placing a page image. The result is editable, but the layout is reconstructed by heuristics, so multi-column pages, tables and tight spacing are the first things to drift.

RouteWhat you getWhere it wins
PowerPoint → File → OpenEvery page rebuilt as editable shapes and text frames. No page image is kept.You already have PowerPoint and the source is a simple single-column document.
Acrobat → Export PDF → PowerPointA .pptx built by Acrobat's own layout engine, usually the most faithful text reconstruction available.You already pay for Acrobat Pro and the document is text-heavy and well structured.
Insert → Object → PDFThe PDF as one embedded object on a single slide, not one slide per page.You need a reference document attached to a deck, not converted into one.
Browser converterOne slide per page with a page image, plus live text and ruled tables in Editable mode.Batch work, no licence, and files that should not leave the machine.

The trade is the same one from section 02, just moved into a different app: fidelity against editability. A route that rebuilds the page into shapes gives you more to edit and more to repair. A route that keeps the page as an image gives you an exact copy that resists editing. Acrobat's export sits closest to the first; PowerPoint's own import is the least predictable of the four; the browser converter deliberately sits at the second, and layers text and tables on top only when you ask for them.

What no desktop route gives you

Batch conversion with a per-file report, and the same output on every machine. The desktop routes depend on that app's own importer, which changes between versions and is not something this guide measured or can promise. The converter's rules are the fixed ones documented in sections 03 to 06 — which is also why it names the slides that fell back to an image instead of leaving you to find them.

14What Broke in Our Own Test Deck

Four claims in the first version of this guide did not survive the measurements. They are corrected here, not quietly deleted.

Claim we publishedWhat the test showedNow
"Slides come out presentation-shaped"An A4 page produced 8.26 x 11.69 in portrait slides, not 16:9.Documented in section 05, with the 13.33 in cap.
"Editable means bigger files"Editable was smaller: 126 KB against 239 KB, because its page image is 637 x 900 px instead of 1489 x 2104.File size is stated per test, not as a rule.
"Tables convert to real tables"A ruled grid gave 1 native table. A fill-only table gave 0 tables and 32 text boxes.The border rule in section 04.
"Editable slides stay sharp"77 DPI behind live text against 180 DPI in image mode — fine on screen, soft in print.The DPI table in section 06.

The pattern behind all four: the converter is honest about which slides fell back to images, but it never told anyone the numbers behind the decision. That is what this revision adds.

AFFLIGO conversion completion screen showing the progress ring and per-file done status

The completion screen reports completion per file. When a page cannot be rebuilt, the report names the slide instead of failing the whole deck silently.

15How This Was Tested

The method, so you can repeat it or challenge it.

Five files were built for this page: a 2-page A4 report, a chart with 320 vector segments and 8 characters of text, a scan with no text layer, a ruled 5 x 6 table, and a 20 x 40 in poster page to test the size cap. Each was converted in both modes in Chrome, and the downloaded .pptx was opened as a zip:

MeasurementWhere it comes from
Slide sizeppt/presentation.xml, the sldSz element, divided by 914400 EMU per inch
Page image resolutionPixel dimensions of the embedded JPEG in ppt/media/, divided by the slide size in inches
Native tablesCount of a:tbl elements in the slide XML
Text boxesCount of a:t runs in the slide XML
Page classificationCharacters, vector operations and table count reported by the extractor for that page

Scope, stated plainly: five files on one machine, measured in November 2026. The thresholds are read from the shipped converter, not inferred. Another PDF with different vector content can land on the other side of the 250-operation line, and a page larger than 13.33 in on either axis is squeezed to fit, which changes its aspect ratio.

Primary sources

Format details: ECMA-376 for PPTX and ISO 32000 for PDF. Runtimes: PDF.js and PptxGenJS. Accessibility: WCAG 2.2, SC 1.1.1.

16Frequently Asked Questions

The questions that come up after a deck has already been converted.

Two rules send a page to an image slide. A page with zero characters is treated as a scan. A page with no detected table, more than 250 vector operations and fewer than 150 characters is treated as a complex graphic. Both are reported per slide, so you can see which pages fell back and why.
Slide size copies the PDF page size, capped at 13.33 inches. An A4 page becomes an 8.26 x 11.69 inch portrait slide. To get widescreen, export or print the source as a 13.33 x 7.5 inch PDF first, then convert. Changing slide size after conversion works, but it enlarges the page image and softens it.
Table detection needs drawn border lines. A ruled grid becomes a native PowerPoint table, up to 8 tables per page. A table drawn with only background fills, or with no borders at all, has no lattice to read, so its cells arrive as positioned text boxes. Rebuild those with Insert, Table, or pull the data out with PDF to Excel.
Editable text is rebuilt as PowerPoint text boxes with no font face attached, so it inherits the deck theme font, which is Calibri by default. The PDF font is not embedded or carried over. Fix the whole deck in one pass with Home, Replace, Replace Fonts rather than restyling each box.
Editable mode caps the page image at 900 pixels on the long edge, which is about 77 DPI on A4 and 72 DPI on a 16:9 slide. Image mode renders the same page at 180 DPI. If the deck is going to be printed or shown on a large screen with no edits, convert in Image mode instead.
There is no page-range selector. Extract the pages you need with the Split PDF tool first, then convert the smaller file. It is also faster: rendering happens page by page in the tab, and the converter accepts up to 100 pages per file, 20MB per file and 10 files per batch.
No. The pages are rendered and the PPTX is assembled inside your browser tab, so the file never leaves the device. You can confirm it yourself: open the browser Network tab, clear it, run a conversion, and watch that no request carries your file. The trade-off is that nothing is stored, so a closed tab means the deck is gone.
Only after OCR. Run the scan through OCR PDF first to add a text layer, check that a sentence selects cleanly, then convert in Editable mode. The background stays the scanned page at roughly 77 DPI, so the slide looks the same while the text on top becomes real. Handwriting and phone photos rarely survive OCR well enough to be worth it.
Yes — PowerPoint's own File, Open can import a PDF directly and rebuild each page into editable shapes and text frames. The trade-off is fidelity: multi-column pages, tables and tight spacing are reconstructed by heuristics and often drift, so you repair more than with the browser converter. Use PowerPoint's import when you already have PowerPoint and the source is simple; use the converter when you need batch work, one slide per page with the page image preserved, or files that stay on your machine.

Convert Your PDF to PowerPoint Now

Pick Image for 180 DPI pages or Editable for live text and ruled tables. Free PPTX, built in your browser, no signup.

Open PDF to PowerPoint Tool

Key Takeaways

Karan Kumar, Founder of AFFLIGO

Karan Kumar

Founder & Web Developer at AFFLIGO

Karan built AFFLIGO's PDF to PowerPoint engine — client-side page rendering with PptxGenJS, text-box reconstruction, table detection and per-slide fallback reporting. He tests it against text, table, chart-heavy and scanned pages before every release, and publishes the measurements when they contradict the marketing.

Last reviewed: November 3, 2026. The measurements on this page were taken on a 2-page A4 report, a 320-operation chart page and a text-light scan.