Convert a Picture to Excel on iPhone (no retyping)

The table you need is a picture in your camera roll. A supplier’s price sheet you photographed at a trade show. A parts list a contractor texted you. A screenshot of a pricing table from a website, or of a spreadsheet someone shared in a chat where you can see the numbers but can’t touch them. A photo of the printed schedule taped to the break-room wall. The data is right there — you can read every cell — and it is trapped in a JPEG. Long-press gives you Live Text, which selects the words as a smear with the columns gone. Paste into Numbers and you get one column of fragments. And most “convert to Excel” tools won’t even accept the file, because a photo isn’t a PDF.

This guide is how to convert a picture to Excel on iPhone in 2026: take the image exactly as it exists — HEIC from the camera, JPEG from a text message, PNG screenshot — share it into an AI extractor that reads the photo the way you do, and get back a real .xlsx with the columns separated and the numbers typed as numbers. On iOS 26 with recent hardware, the photo never leaves the phone.

Why the iPhone’s built-in tools can’t finish the job

Apple has taught the iPhone to read images remarkably well. It has not taught it to hand you a table:

Live Text extracts words, not structure. Long-press any photo of a table and iOS will select the text — as lines of words. The spatial relationships that made it a table (this price belongs to that part number, this quantity to that row) are discarded at copy time. What lands in Numbers is dates, then descriptions, then amounts, interleaved in recognizer order.
Photos has no “export as table” anywhere. You can copy a subject out of a photo, look up a landmark, translate a sign. There is no path — in Photos, Files, or the share sheet, through iOS 26 — from a photographed table to a spreadsheet.
Screenshots are pictures too. A screenshot of an Excel file in a chat, a web dashboard, or a PDF preview has exactly the same problem as a photo of paper: it is pixels. The fact that the source was digital doesn’t help; the structure didn’t survive the screenshot.
Web converters mostly want PDFs. The tools that advertise image support run classic OCR: recover characters and positions, then guess column boundaries from pixel gaps. On a real phone photo — perspective from shooting at an angle, a shadow across the sheet, uneven lighting — the guesses collapse into fragment soup. And you uploaded the image to get that result.

The gap is specific: the phone can read the characters, but nothing built in understands the table.

What actually works: AI that reads the photo, on the phone

ignitai takes images directly — HEIC, JPEG, PNG, screenshots — no PDF wrapper required. It reads the photo the way a person does: recognizes the table as a table, headers and rows and the relationship between a quantity and its line total, and writes that understanding straight into a spreadsheet. Character recognition and structure understanding happen in one step, so there is no separate OCR pass whose column-guessing errors you inherit.

The full iPhone flow:

Share the picture into ignitai. From Photos, Messages, Mail, or Files: tap Share → ignitai. (If it isn’t listed, scroll right in the share sheet and tap “Edit Actions” to enable it.) You can select several photos at once — five snapshots of a five-page price list is one job.
Say what you want, in plain English. For a photo that is mostly table — a price list, a schedule, a receipt — skip the prompt and let ignitai take everything. For a busier image, one sentence picks the data out of the noise:

“Extract the parts table: part number, description, unit price. One row per part. Ignore the logo, the handwritten circle, and everything below the table.”

Prompts matter more on photos than on clean PDFs, because photos contain the world — a thumb at the frame edge, glare, the tabletop around the page — and naming what you want tells the model what to ignore. Save the prompt as a preset for the next one.
Choose Excel (.xlsx) as the output. Column types are set during extraction: dates become dates, prices become numbers with currency formatting. The sheet opens in Numbers or Excel for iOS ready to sort and sum — not as text pretending to be numbers.
Tap Extract. On an iPhone 15 Pro or newer running iOS 26, the extraction runs entirely on-device via Apple’s Foundation Models framework — the photo is read on the phone and the .xlsx is written on the phone. A single image takes seconds. On older hardware or iOS versions, ignitai falls back to a hosted pipeline with documented zero retention.
Review the preview, then save. Spot-check the first and last rows against the photo, then save to Files, iCloud Drive, or straight into a share to whoever asked for “that list in a spreadsheet.”

Total user time: under a minute from camera roll to .xlsx.

Taking a better picture, when you’re the photographer

Half the images in this workflow arrive from someone else, and you work with what you got. But when the paper is in front of you and you hold the camera, thirty seconds of care saves a re-shoot:

Shoot square-on, not at an angle. Perspective distortion is the single biggest quality lever. Hold the phone parallel to the page, directly above it.
Kill the shadow. Your own shadow across the table is the classic self-inflicted defect. Step aside or turn the page toward the light.
Fill the frame with the table. The table should be most of the image. If it’s a wall poster, get close; crop in Photos afterward if needed.
One page per photo for unlike documents. A photo per page beats one photo of two pages side by side.
If the document matters, scan instead of photographing. The Notes and Files document scanner deskews and normalizes lighting at capture, and produces a multi-page PDF — for anything longer than a couple of pages, the scanned-PDF-to-Excel workflow on iPhone is the more durable habit. The photo path in this guide is for the pictures that already exist and the moments when the camera is faster than the ritual.

Receipts, as ever, are their own case: crumpled thermal paper photographed on a car seat is a solved problem, but a specifically handled one — the receipt-to-spreadsheet workflow on iPhone covers it end to end.

Screenshots: the digital table you can see but not touch

The screenshot case deserves its own note because it feels like it should be easier, and isn’t. Someone posts a rate table in a group chat as a screenshot of their spreadsheet. A SaaS dashboard shows a table with no export button. A PDF preview in a chat app renders the page but won’t give you the file. In every case you hold a PNG of a table.

The workflow is identical: Share → ignitai → prompt if needed → Excel. Screenshots are actually the easy case — perfectly flat, evenly lit, machine-rendered type — and extract essentially without error. The one habit worth keeping: if the table is longer than one screen, take overlapping screenshots as you scroll and select them all as one job; ignitai writes one sheet and you delete the duplicate boundary rows in the preview.

Batches: many pictures, one sheet

The realistic version of this job is rarely one photo. It’s fourteen pictures of receipts from a work trip, or six photos of a supplier’s catalog pages, or a month of texted delivery manifests:

In Photos, select them all. Share → ignitai.
One prompt (or your saved preset) applies across the batch.
The output is a single .xlsx, one row per record, with a source_file column tying every row back to its image — so fourteen receipt photos become one expense sheet you can subtotal by day.
Images that fail — a blurry frame, an accidental pocket shot — are listed separately, so you re-shoot or re-run only those.

A phone-sized batch is a dozen images. If what you actually have is a folder of hundreds of images accumulated on a drive, that’s a desk job: the Mac batch workflow takes a folder in one drag, same pipeline, same presets.

A worked example: the trade-show price sheet

You’re at a supplier’s booth. Their printed price sheet — eighty SKUs, unit prices, case quantities — is on the table, and you want it in Excel tonight to compare against your current vendor:

Photograph the sheet square-on. Two photos if it’s two pages.
That evening: select both photos → Share → ignitai.
Prompt: “Extract every product row: SKU, description, unit price, case quantity. One row per product. Ignore the header, footer, and the salesperson’s handwriting.”
Output: Excel. Tap Extract. Both pages finish in seconds.
In the preview, confirm the last SKU on page two made it. Save to iCloud Drive.

Open it next to your current vendor’s sheet and the comparison is a VLOOKUP away — from two photos taken standing at a booth. If the output should land in Apple’s spreadsheet instead, the PDF-to-Numbers flow on iPhone is the same pattern with a different output pick.

The verification habit: make the sheet reproduce the picture

Extraction from a photo deserves the same one-formula check as extraction from any scan: make the spreadsheet reproduce a number visible in the image. If the photographed sheet prints a total, =SUM() the column and compare. If it doesn’t, count: eighty SKUs in the photo should be eighty rows in the sheet.

Match: done — the sheet is trustworthy.
Mismatch: sort the column and scan the extremes. A glare spot turning an 8 into a 3 is findable in a minute, and the fix is re-shooting one photo, not redoing the job.

A spreadsheet built from a picture is only as good as the one number you verified. Verify one.

A note on privacy

Photos of documents are documents. A photographed pay statement, a texted medical bill, a screenshot of an account page — uploading them to a web “image to Excel” converter is uploading exactly the content the paper version would have protected. On-device extraction on iOS 26+ means the image is read on your iPhone and the Excel file is written on your iPhone; nothing leaves the device. The same caution that applies to bank statements on iPhone applies to a photo of a bank statement — it’s the same data wearing a different file extension.

Bottom line

A picture of a table — camera photo, texted JPEG, screenshot — contains data the iPhone can read but can’t structure: Live Text gives you word soup, Photos has no table export, and web converters guess columns from pixels and lose. The workflow that works in 2026: Share the image into ignitai straight from Photos or Messages, name the table in one plain-English sentence if the image is busy, export .xlsx with the types already set, and verify one visible number. On an iPhone 15 Pro or newer with iOS 26, the photo never leaves the phone. Use this path when the picture already exists or the camera is faster than the scanner; when the paper matters and you’ll process it in bulk, capture it with the document scanner and take the scanned-PDF path instead.

Get ignitai on the App Store — free download, $19.99/mo unlocks unlimited extractions and batch mode after the 3-day trial.

FAQ

What image formats can I convert to Excel on iPhone?

HEIC (the iPhone camera’s default), JPEG, PNG, and screenshots all work — shared directly from Photos, Messages, Mail, or Files into ignitai. No conversion to PDF is needed first; the image is read as-is and the output is a standard .xlsx that opens in Excel, Numbers, or Google Sheets.

Can I convert a screenshot of a spreadsheet back into a real spreadsheet?

Yes, and screenshots are the easiest case — flat, evenly lit, machine-rendered text extracts essentially without error. For a table longer than one screen, take overlapping screenshots while scrolling, select them all as one job, and delete the duplicate boundary rows in the preview.

Does converting a photo to Excel work without internet?

On an iPhone 15 Pro or newer running iOS 26, yes — ignitai runs the extraction on-device using Apple’s Foundation Models framework, so it works in airplane mode and the photo never leaves the phone. Older iPhones fall back to a hosted pipeline with documented zero retention, which requires a connection.