Topdon TopInfrared images won’t import into TopView (PC)?
You’re not doing anything wrong — this is a common question, not a bug.
Mobile images and PC software handle thermal data differently, which is why exported JPGs from the TopInfrared app don’t show up in TopView.
You take photos in the TopInfrared Android/iOS app, copy the images to your PC, and then TopView won’t show them or import them. Even though they’re “.jpg”, even though they look like thermal images, and even though you can still tap points in the mobile app and read temperatures.
This post explains what’s happening under the hood, step by step, in plain terms.
1) What You Think Is Happening vs What’s Actually Happening
What it feels like as a user:
“If I can open the picture later in the TopInfrared app and still read the temperature at any point, the temperature data must be stored inside the image file.”
What’s actually happening:
There are usually two different things involved when you capture an image on mobile:
- A normal visual image file (JPEG) that you can see in your gallery / export / share
- A separate thermal data record that the app keeps internally so it can do measurements later
So when you export/copy the photo to a PC, you typically bring only the visual JPEG, not the thermal “brain” behind it.
2) What the Mobile App Saves (and Why It’s Done This Way)
When you take a snapshot in TopInfrared, the app saves a standard JPEG that looks like a thermal image (palette colours, overlays, etc.).
That JPEG is efficient:
- easy to preview instantly
- easy to share on WhatsApp/email
- small file sizes compared to raw sensor data
- works with the phone’s normal photo storage
From a mobile design point of view, this is a very practical approach. Phones are built around fast image viewing and quick sharing, and most users want a simple “photo-like” output.
3) “But I Can Still Measure Temperatures in the App…” (And How You Can Prove What’s Happening)
This is the part that confuses people the most — and there’s actually a simple way to prove what’s going on.
Inside TopInfrared, you can:
- open a saved capture
- move a cursor or spot
- place points or boxes
- get an exact temperature readout
At first glance, that makes it feel like the temperature data must be stored inside the JPEG itself.
However, what’s really happening is this:
- TopInfrared shows you the JPEG image as the visual layer
- When you place a measurement point, the app reads temperature values from a separately stored thermal data file
- That thermal data is linked to the image by its filename / internal reference
You can actually test this yourself:
- Take a thermal photo in the TopInfrared app
- Open your phone’s file manager
- Find the saved image and rename the file
- Go back into TopInfrared and try to edit or measure that image again
What you’ll notice is:
- The image may still appear
- But the thermal measurement data is suddenly missing
- You can no longer read temperatures or place measurement points
That happens because the app no longer recognises the renamed image as being linked to its internal thermal data record. The image and the thermal data were never a single self-contained file — they were two separate things associated by name/reference.
This is the key reason why exported images lose their measurement capability once they leave the app.
4) What TopView (PC) Is Expecting
TopView on PC isn’t just a viewer — it’s a thermal analysis tool.
For analysis, it needs a file that contains:
- the raw thermal sensor matrix (temperature per pixel)
- calibration information (how to convert raw readings into temperatures)
- camera/device metadata
- environmental parameters (often emissivity, reflection, distance, etc.)
That’s why in TopView you can often:
- change palettes after the fact
- move measurement points and get valid readings
- generate reports with real thermal numbers
So TopView filters for files that contain that full “radiometric” package. If it doesn’t detect the expected internal data structure, it won’t treat it as a compatible thermal file — even if the extension says “.jpg”.
) Why Copied Mobile JPEGs Don’t Appear in TopView Import
This is why you see behaviour like:
- “My files don’t show up in the selection window”
- “Copying to C:\ doesn’t help”
- “Changing resolution or renaming doesn’t help”
- “It only imports if I capture with the camera connected”
TopView isn’t scanning for “any JPG that looks thermal”.
It’s scanning for “files that contain the correct thermal data payload”.
If the mobile export is essentially:
- a palette-rendered JPEG (visual only)
- without the radiometric data block TopView expects
Then TopView will ignore it, because it can’t perform real analysis on it.
6) Practical Takeaways and Best Workflow
This isn’t Topdon doing something “silly” — it’s simply two systems optimised for different use cases:
- Mobile app: fast capture, efficient storage, easy sharing
- PC software: accurate analysis, measurement integrity, calibrated data
So the right workflow depends on what you want to do:
- For PC analysis: capture images through TopView while connected
- For quick snapshots and sharing: mobile exports are perfect
- For advanced users: only access to the mobile app’s internal thermal data (not the JPEG) would allow cross-platform analysis