How to Extract Images from a PDF on iPhone
Choose original-picture extraction, a rendered page or OCR, then inspect the saved file. Includes scoped iPhone observations and version 1.02 source notes.
PDF ExtractorThe short answer
Open a PDF, choose image extraction, inspect the recovered pictures and export the selection. Version 1.02 lists an allowance of 20 supported images before full access. This guide remains an iPhone/iPad method; the app also lists Mac support, but those controls have not been reproduced here.
What changed in version 1.02
Version 1.02, released October 23, 2026, adds Word (.docx), Markdown, HTML and RTF conversion and documents Mac, iPhone and iPad support. The listing describes local processing and on-device OCR. Earlier iPhone image-extraction results below concern version 1.01, not a new conversion or Mac test.
Use the linked Word guide if your goal is editable text rather than separate pictures. The historical image-selection screenshots do not illustrate the refreshed conversion interface.
Choose the output before choosing an app
To reuse a photograph, look for embedded-picture extraction. To share what the entire page looks like, export or capture a rendered page. To copy words from a scan, use OCR. These operations produce different outputs, even when an app places them under similar PDF tool menus.
A vector diagram may contain no embedded raster picture. An extraction grid can therefore omit that diagram without losing a source photo. A screenshot includes the page background and display scaling; it is not evidence that original pixels or transparency were preserved.
1. Open a PDF you can inspect
Keep a source copy in an accessible file location. Use the opening action in your installed release and verify the filename. Begin with a small non-sensitive document containing a picture you recognize.
2. Choose image extraction, not document conversion
Use the picture-extraction workflow and inspect the selection. Word conversion reflows content into a document; it is not the same operation as saving an embedded picture. Exact version 1.02 controls are not documented by the older screenshots, so follow the labels in your release.
3. Preview and export the pictures you need
Select the relevant pictures, review them and use the available save or share action. The current description includes Photos, file export and packaging multiple images as ZIP. Destinations depend on the platform and installed apps.
The provider describes up to 20 supported images in free use and unlimited supported-image extraction after the one-time unlock. That allowance is a documented term, not a new device observation.
4. Inspect the actual saved file
Check dimensions, orientation and transparent areas outside the app. Keep the original PDF for comparison. Our version 1.01 save-path sample lost alpha; no version 1.02 retest is attached, so preservation of transparency is neither promised nor ruled out for the new version.
What the supplied iPhone sample establishes
The October 18 evidence concerns PDF Extractor 1.01 and iLovePDF 4.1.0 on a tester-reported iPhone Air running iOS 27.0.1. PDF Extractor returned four PNGs; the iLovePDF follow-up returned three JPGs, consistent with three unique raster assets and one repeated placement. Four versus three is not a completeness score.
Both returned the reference dimensions in this small sample; neither returned transparency. The PDF Extractor RGB and scan samples matched the reference RGB pixels, while the JPG pixels differed. This does not establish a universal quality winner or a result for PDF Extractor 1.02.
Our small-sample findings
Both apps recovered the three unique pictures. PDF Extractor saved PNGs to Photos; iLovePDF returned JPGs. Neither preserved the transparent sample. These findings apply to this iPhone run, not every PDF.
Read the test results, method and limitations
PDF Extractor 1.01 returned four PNGs; iLovePDF 4.1.0 successfully returned three JPGs in the follow-up. The fixture contains three unique raster assets placed four times, so three outputs are consistent with resource deduplication, not a missing unique picture. Both retained the sample dimensions; neither returned transparency. PDF Extractor matched the RGB/scan reference pixels, while iLovePDF JPG pixels differed. This limited sample is not an overall ranking; no comparative winner is established.
Known limitation: transparency was not preserved in this saved output. The input contains an RGBA image and a PDF soft mask; the returned 320 × 320 PNG is RGB, with every decoded alpha value equal to 255. We have not isolated whether the loss occurred during extraction, saving to Photos or subsequent transfer. Do not describe this path as lossless for transparent images.
PDF Extractor: returned PNGs
| Sample | Returned dimensions | Observed result |
|---|---|---|
| Repeated RGB picture | 640 × 480, twice | Both returned PNGs match the reference RGB pixels and dimensions. Their file hashes also match each other. |
| Transparency sample | 320 × 320 | Transparency not preserved: returned PNG is RGB, not RGBA. Color channels match, but the alpha channel is absent. |
| Synthetic scanned image | 800 × 1100 | Returned PNG matches the reference RGB pixels and dimensions. |
| Vector-only page | No raster picture expected | No additional vector-chart picture appears among the four returned exports. This is not a missing embedded raster image. |
Workflow and access
The PDF Extractor recording begins with the test PDF already open. It shows image selection, saving four images to Photos, the photo-add permission prompt and opening a saved result. No purchase prompt is visible in this run; the tester reports no paid entitlement. This demonstrates this four-image save only—not an unlimited free allowance or a verified import walkthrough.
iLovePDF: successful follow-up, three unique images
The first import attempt was blocked, but the follow-up recording shows importing the fixture through Documents, choosing PDF to JPG → Extract images, and completing extraction. Three JPGs were returned: 640 × 480, 320 × 320 and 800 × 1100. All three unique raster assets are represented; the repeated placement is not a fourth unique image. This is consistent with deduplication, not proof of a missing picture.
The JPGs retain those dimensions but do not match the reference pixels exactly. JPG output does not preserve alpha transparency. The recording shows one free task remaining out of two for that day after completion; this is an observed counter, not a guarantee of future pricing or allowances.
Sharing friction (tester-reported): saving to Photos was not straightforward, and the tester appeared to need individual AirDrop transfers to the Mac. The supplied recording ends at the results list; it does not demonstrate the sharing attempts or rule out a batch-share option. Batch saving and sharing remain unverified—not established as unsupported.
Device, method and remaining limits
iPhone Air · iOS 27.0.1 (tester-reported). App versions supplied by the tester: PDF Extractor 1.01; iLovePDF 4.1.0. The results apply to the supplied sample and recorded workflow.
We inspected the initial recordings, the successful iLovePDF follow-up, four returned PNGs and three returned JPGs. Comparisons use decoded pixels, not file size or thumbnail appearance. The table above describes PDF Extractor outputs; the iLovePDF findings are separately described below it. The two repeated RGB outputs are intentional placements of one source image, not two distinct source assets. Pixel equality here does not imply identical file encoding, metadata or color-profile behavior.
The recording visually identifies our four-page synthetic fixture, but no input PDF was returned for a byte-level identity check. The controlled reference has three raster assets placed four times, plus a vector-only page. These findings concern this sample and save path only.
Still untested: iPad, batch-sharing options, other save/share destinations, broader free limits, large and protected PDFs, offline operation and network traffic. No speed benchmark or privacy certification is claimed. Raw recordings are not published because they include personal gallery content.
Limitations & considerations
- The October 18 image evidence concerns PDF Extractor 1.01 on iPhone. Its returned transparency sample lost alpha. Version 1.02 has not been retested for this issue; do not claim it is fixed or unchanged.
- Word/OCR quality, complex tables, reading order and layout fidelity have not been benchmarked. Reflowed output is editable content, not a guarantee of matching page composition.
- Mac availability and local processing are described by the provider, not independently verified. Check Mac system requirements and purchase eligibility; no Intel support, automatic sync or cross-device purchase-restoration guarantee is established here.
- The stated free allowances and one-time purchase come from the version 1.02 description. Confirm the current local checkout amount and access before a large export; the older $2.99 listing is not a newly verified price.
Documented features, attributed opinions and explicitly labeled hands-on observations are different kinds of evidence. We do not infer unmeasured performance or privacy guarantees.
Sources & scope
Reviewed October 24, 2026. These are provider-published sources; listings and feature access can change. The separate first-round observations above use supplied recordings, four PNGs and three JPGs, with known transparency limitations and unverified batch-sharing options.
- PDF Extractor 1.02 · live Apple metadata
Checked October 24, 2026; released October 23. Documents Word (.docx), Markdown, HTML and RTF conversion, local OCR, Mac/iPhone/iPad support and specific free allowances. Provider statements, not a new device benchmark.
- PDF Extractor · App Store
Current product listing; historical screenshots are not a current conversion walkthrough.
No comments yet. Be the first to share your experience.