Your import needs records, but your source is a photograph
Prepare comma-separated records from a photographed table when your destination needs CSV rather than a workbook. Review the recognized values before export, then choose the right column types in the application that imports them.
Image-only lists for a data pipeline
Turn a photographed reference list into a reviewed CSV input for a script, keeping your own validation between OCR and downstream processing.
Moving camera-captured prices into Sheets
Prepare plain rows that Google Sheets can import, then select the correct locale for decimal and date interpretation.
Prepare camera-captured rows for a CSV import
- Use a sharp JPG with complete column headings and no glare across the values.
- Correct recognition errors and confirm each row has the expected fields.
- Export CSV and inspect a small import before loading the full file into your destination.
Photo extraction, delimiters and lost number formats
- What does a JPG to CSV result contain?
- It contains the recognized table values as delimited text. It does not include the original photograph, worksheet styling or image metadata.
- Can changing the .jpg extension to .csv convert my table?
- No. Renaming a file does not read its pixels. OCR must recognize the visible values before they can be written as CSV records.
- Why do imported photo values appear in one column?
- Check the import delimiter in your destination. Use its CSV import dialog and confirm the column preview before completing the import.
- Will CSV remember the number format shown in the photograph?
- CSV stores text fields without workbook cell formats. Set dates, identifiers and numeric formats in the importing application after checking the values.
