Your FLIR images, unpacked into numbers and photos.
A FLIR thermal JPG looks like one colored picture, but the temperature of every pixel is stored inside it, and often a normal photo too. ThermalUnpack reads a whole batch and gives you a CSV of temperatures per image, the hidden visible photo, and a summary with min, max and mean, right in your browser.
- Nothing uploaded, no account
- No FLIR Tools, no Python, no ExifTool
- A whole batch at once
At a glance
What ThermalUnpack does and doesn’t do
- Works withRadiometric
.jpgfiles saved by FLIR thermal cameras. Tested with real files from FLIR E5, FLIR T640, FLIR SC660, FLIR AX8, FLIR b60 and FLIR ONE. Other FLIR models that save radiometric JPGs should work, but are not tested. - ExtractsThree things, for a whole batch. A CSV with the temperature of every pixel of each image, in °C or °F. The visible photo hidden inside the file, when it has one. And a
summary.csv: camera model, date, thermal resolution, min, max, mean, emissivity, reflected temperature, distance and more. - Runs onThe browser, on Windows, Mac, iPhone and Android. Nothing to install. It does not need FLIR Tools, Python or ExifTool.
- Free25 images per batch, with every CSV, photo and the summary. Full: $9 one-time, whole batches.
- PrivacyNothing is uploaded. No account. Your images stay on your device.
- Doesn’tRead thermal images from Seek, HIKMICRO or InfiRay, or FLIR videos (
.seq,.csq). It does not change emissivity: it uses the values stored in each file. It is not a certified measuring instrument.
- Excel
- Google Sheets
- MATLAB
- Python
- R
- ImageJ
average difference from FLIR’s own ThermaCAM Researcher Pro on a real 640 × 480 image
How we checkedof your thermal images sent to any server
How it worksimages unpacked free per batch, with every CSV and photo
Try itonce, whole batches, no subscription
PricingThe problem
The numbers are in the file. Getting them out is the hard part.
“How do I export the temperature of each pixel from my FLIR images to CSV? FLIR Tools is gone and I have 200 pictures.”
FLIR Tools is discontinued
FLIR lists FLIR Tools as discontinued. Its replacement, FLIR Thermal Studio, has a free Starter plan, but CSV export is only in the paid subscriptions.
The free route is a script
The usual advice is a Python script such as FlirImageExtractor, or Thermimage in R. Both need ExifTool installed, a command line, and some debugging when your camera stores the data differently.
The photo is hidden too
Cameras with two lenses save the normal photo inside the thermal JPG. Photo apps only show the colored thermal picture, so the photo you need for the report stays out of reach.
How it works
Three steps. No FLIR Tools, no Python, no ExifTool.
- Step 1
Copy the JPGs off the camera
Use the original
.jpgfiles from the camera’s memory or from the FLIR app’s export. Images that went through a chat app or an editor lose the thermal data. What is inside the file - Step 2
Add the batch here
Drop the files or a whole folder. ThermalUnpack finds the FLIR data in each JPG, decodes the raw thermal image and converts it to temperatures with the constants stored in that file.
- Step 3
Download the ZIP
One CSV of temperatures per image, the visible photo of each image that has one, and a summary.csv for the whole batch. Min, max and mean are also shown on the page.
Unpack
Add your FLIR thermal images
Everything runs on this page. Your images never leave your device.
Drop your FLIR .jpg files or a folder of them here
The original radiometric JPGs from a FLIR camera or the FLIR ONE app. Nothing is uploaded.
Temperatures are computed with the emissivity, reflected temperature and distance stored in each file, as set on the camera. They are listed in summary.csv.
Free: 25 images per batch, with every CSV, photo and the summary. Unlock whole batches for $9.
Plain files
Numbers you can open anywhere.
No special viewer and no proprietary format. The ZIP holds CSV files and ordinary pictures, named after your images.
- name_temps.csvThe temperature of every pixel: one line per row of the thermal image, two decimals, no header. A 640 × 480 image is 480 lines of 640 values.
- name_visible.jpgThe normal photo the camera stored inside the file, at its full size, exactly as stored. Older cameras store a PNG; it is converted to normal colors.
- summary.csvOne line per image: camera, date, resolution, min, max, mean, and every setting and calibration constant used for the conversion.
File, Camera model, Thermal size, Min (°C), Max (°C), Mean (°C), Emissivity
FLIR0132.jpg, FLIR E5, 320 × 240, 15.75, 73.66, 27.56, 0.95
FLIR_T640.jpg, FLIR T640, 640 × 480, 25.46, 97.85, 36.91, 0.95
IR_2412.jpg, FLIR SC660, 640 × 480, 22.74, 35.25, 28.26, 0.9523.73,23.72,23.63,23.59,23.59,23.69,23.55,23.42,…
23.64,23.67,23.65,23.59,23.56,23.56,23.53,23.41,…
23.59,23.59,23.59,23.56,23.57,23.53,23.56,23.41,…What you get back
Every pixel as a temperature, every hidden photo as a file.
A FLIR JPG carries the raw sensor reading of each pixel and the calibration of the camera that took it. ThermalUnpack does the conversion file by file.
A temperature for every pixel
One CSV per image with the full matrix: 76,800 values for a 320 × 240 camera, 307,200 for a 640 × 480 one. In °C or °F.
The visible photo
The normal picture the second lens took, pulled out of the JPG at its full size. Handy for reports, where the thermal picture alone is hard to place.
A summary of the batch
summary.csv lists camera model, date, resolution, min, max and mean per image, plus emissivity, reflected temperature, distance, humidity and the Planck constants.
The camera’s own calibration
Raw values are converted with the Planck constants, emissivity, reflected temperature and atmospheric transmission stored in each file. Nothing is assumed.
Whole batches
Add a folder from an inspection or a field day. Images are processed one after another; a file that is not a FLIR image gets a clear note and the batch goes on.
Private
There is no upload step and no account. Your images are only read; you get a new ZIP.
Compared
Three ways to get the data out of a FLIR JPG.
The script route is free and flexible, and FLIR’s own software does much more than export. ThermalUnpack is for getting the temperatures and the photo out of a batch without installing anything.
| Feature | ThermalUnpack | Python or R scripts with ExifTool (FlirImageExtractor, Thermimage) | FLIR Thermal Studio Pro |
|---|---|---|---|
| What it is for | Getting temperatures (CSV) and the visible photo out of a batch of FLIR JPGs | The same, inside your own code; the usual free advice | Full thermal analysis, editing and reports, from FLIR |
| Cost | Free for 25 images per batch, $9 once for whole batches | Free | Paid subscription |
| What you install | Nothing | Python or R, the script’s packages and ExifTool | A desktop program |
| Works on a phone | Yes, in the browser | No | No |
| Temperature of every pixel as CSV | Yes | Yes | Yes |
| Visible photo extracted | Yes | Yes | Yes |
| Batch with one summary file | Yes: summary.csv | If you script the loop | Yes, its own batch tools |
| Change emissivity and recompute | No: uses the values in the file | Yes, in code | Yes |
| Palettes, measurements, reports, video | No | Partly, in code | Yes |
| Files leave your device | Never | Never | No, it is a desktop program |
Pricing
Free for 25 images per batch. $9 once for whole batches.
Start free
Free
Unpack the first 25 images of each batch, with nothing held back for those images.
Unpack my FLIR images- Temperature CSV for each image, °C or °F
- The visible photo of each image that has one
- summary.csv and the results table
- No account
ONE-TIME
ThermalUnpack Full
one-time · whole batches · any number of batches
Unlock whole batches, $9- Every image in the batch, not only the first 25
- Whole folders from an inspection or a field day
- Run it again on future images
- No subscription
FAQ
Questions about getting data out of FLIR images
Want the long version? Read the guide.
Read the guideHow do I get the temperature of every pixel out of a FLIR JPG?
Add the .jpg files your FLIR camera saved to ThermalUnpack. For each one it writes a CSV file with one number per pixel: a 320 × 240 thermal image gives 240 rows of 320 temperatures, in °C or °F. You download everything as one ZIP. This works because a FLIR camera stores the raw reading of every pixel inside the JPG, next to the picture you see, together with the calibration constants needed to turn those readings into temperatures.
What is a radiometric JPG, and how do I know mine is one?
A radiometric JPG is a thermal picture that also carries the measured data of every pixel, not only the colors. FLIR cameras such as the FLIR ONE, the C, E and T series and the AX8 save this kind of file. The simplest check is to add the file here. If it is radiometric you get its temperatures; if it is not, the row says "No FLIR thermal data inside". A FLIR image that was sent through a chat app, screenshotted or saved again by a photo editor usually loses the data.
Where is the normal photo, and do all files have one?
Cameras with a second, visible-light lens (FLIR ONE, E5, T640, AX8 and many others) store the full normal photo inside the same JPG, even when the picture you see is only thermal or a blend. ThermalUnpack saves it as name_visible.jpg, or name_visible.png for older cameras that store a PNG. Files from cameras without a visible-light lens, or saved in a mode that leaves the photo out, have none; the table says "none inside". Of the 8 real files we tested, 6 had a visible photo.
Which FLIR cameras does it work with?
Tested with real files from: FLIR E5, FLIR T640, FLIR SC660, FLIR AX8, FLIR b60 and FLIR ONE (two files saved by the FLIR ONE app; they do not say which generation). Other FLIR cameras that save radiometric JPGs use the same file layout and should work, but we have not tested them: the rest of the E, T and C series, FLIR ONE Pro and Edge, the Exx series, A series and older B and i series, and DJI Zenmuse XT and XT2 cameras that have a FLIR core. If a file from your camera fails, email it to support and we will look at it.
How are the temperatures calculated?
With the standard radiometric formula and the numbers stored in your own file. Each raw value is corrected for emissivity, reflected temperature and atmospheric transmission (from distance, air temperature and humidity), and then converted with the camera’s Planck calibration constants R1, R2, B, F and O. Those constants are specific to each camera and are saved in every image. The summary lists every value that was used.
How accurate are the numbers?
We compared the output with independent references for real files. For a FLIR SC660 image, the temperatures that FLIR’s own ThermaCAM Researcher Pro software exported for all 307,200 pixels are published; with the same emissivity, ThermalUnpack differs from them by 0.03 °C on average and 0.11 °C at most. For a FLIR E5 image, the minimum, maximum and average the camera printed on the picture (66.3, 164.6 and 99.8 °F for the box it drew) match to 0.1 °F. For the FLIR AX8, T640, SC660 and b60 test files the values agree with the readouts printed on the images within 0.5 °C; the two FLIR ONE files have no printed readout to compare with. ThermalUnpack is not a certified measuring instrument: for regulated inspections use the software your procedure names.
Why are my min and max different from the scale printed on the image?
Usually for one of four reasons. The scale on the picture can be locked by hand, so it is not always the real minimum and maximum. A value printed on the image often belongs to a spot or a box, not to the whole frame. Cameras tend to ignore the outermost pixels, while the CSV holds all of them: in our FLIR T640 test file the hottest pixel sits on the left edge and reads 208.1 °F, while the camera printed a maximum of 199 °F; without the outermost pixels ThermalUnpack reads 199.6 °F. And very cold or very hot areas, such as a clear sky, can read beyond the limits the camera clips its readings at; those pixels are left out of min, max and mean, and the note says how many.
What does the CSV look like?
Plain numbers separated by commas, with no header: one line per row of the thermal image, one value per pixel, two decimals, top-left pixel first. A 640 × 480 image is 480 lines of 640 values, about 1.8 MB. It opens in Excel, Google Sheets, MATLAB, Python, R or ImageJ. A pixel whose raw value is below what the calibration can express is left empty.
What is in summary.csv?
One line per file: file name, status, camera model, date taken, thermal width and height, min, max and mean, emissivity, reflected temperature, object distance, atmospheric temperature, relative humidity, IR window temperature and transmission, the Planck constants R1, R2, B, F and O, the camera’s range, lens, field of view, serial number and camera software, how the raw image was stored, the names of the CSV and photo that were written, and a note. Files that could not be unpacked are listed too, with the reason.
Can I change the emissivity or the reflected temperature?
Not in this version. ThermalUnpack uses the emissivity, reflected temperature, distance, humidity and air temperature that were set on the camera when the picture was taken, and lists them in summary.csv so you can see what each image was computed with. If you need to recompute with other values, FLIR Thermal Studio or the Thermimage package for R can do that.
Can I get °F instead of °C?
Yes. Choose °F before or after adding the files; the run repeats on its own. The CSVs, the table and the summary all use the unit you picked. °C is the default.
Does it read Seek, HIKMICRO, InfiRay, Fluke or DJI images, or .seq and .csq videos?
No. It reads radiometric JPGs written by FLIR cameras. Thermal images from Seek, HIKMICRO, InfiRay, Fluke, Testo and other brands use other formats and are reported as "No FLIR thermal data inside". The same goes for the R-JPEG files of newer DJI drones (H20T, Mavic 2 Enterprise Advanced, Mavic 3T), which use DJI’s own format. FLIR videos (.seq, .csq) and .fff files are not read.
Why does my file say "No FLIR thermal data inside"?
Because the JPG has no FLIR data block. That happens when the image is a normal photo, when it comes from another brand of thermal camera, or when a FLIR image was saved again by an app that drops the hidden data: sent through WhatsApp or Messenger, screenshotted, cropped in a photo editor, or exported from a gallery app. Use the original file from the camera or from the FLIR app’s export.
Are my thermal images uploaded anywhere?
No. The files are read and the ZIP is built by JavaScript on this page, on your device. There is no upload step and no account. The only network requests are for the page itself, cookieless page analytics, and the payment check if you buy the full version, which sends a payment ID and never a file.
Do I need FLIR Tools, Python or ExifTool?
No. Nothing is installed. FLIR Tools has been discontinued, and the usual free route is a Python script that calls ExifTool. ThermalUnpack does the same job in the browser, on Windows, Mac, iPhone and Android, for a whole batch of images at once.
How many images can I add at once?
As many as your device has memory for. Images are processed one at a time and each CSV is compressed into the ZIP as it is made. We ran a batch of 300 images on a computer without trouble. The ZIP of one batch can hold up to 4 GB. On a phone, keep batches smaller.
How does the $9 full version work?
Free processes the first 25 images of each batch, with every CSV, visible photo and the summary. The full version is a single $9 payment, with no subscription and no account, and processes whole batches of any size, as many times as you like. It unlocks in the browser you pay from.
Get the numbers out of your thermal images.
Add your FLIR JPGs and download the temperature of every pixel as CSV, the hidden visible photos and a summary of the batch. The first 25 images of each batch are free.