Thermal Camera Buying Guide: Radiometric File Evidence
A thermal image can look convincing in an ordinary photo viewer while important measurement information remains hidden or absent. Ask for a complete sample-file workflow before purchasing the camera, software and storage arrangement.
For: U.S. NDT equipment coordinators, quality staff and inspection business owners
Decide whether you need a picture or a reusable measurement record
Start with the intended deliverable. A visual illustration, a screening observation and a retained radiometric record serve different purposes. Ask the technical owner what information must remain available after capture and who will review it. A colorful image with a temperature label may be enough for one communication task and insufficient for another. The purchase request should describe the required record rather than simply asking for JPEG export or thermal reporting software. That distinction affects camera capabilities, licenses and the eventual handover process.
Keep the equipment selection separate from the thermographic procedure. This guide does not prescribe emissivity values, measurement distances, temperature thresholds or diagnostic conclusions. Those require the appropriate technical process and conditions of use. Procurement can still test whether the proposed package preserves the required evidence and whether recipients can read it. Define the decision and record needs first, then ask suppliers to demonstrate the exact camera, lens, software and file-transfer path that would satisfy them.
Understand why the JPEG extension is not enough
FLIR's T8xx image-file documentation describes files that contain thermal and visual information, including a radiometric component and an ordinary image component for general viewing. The practical lesson is that a file can display as a normal photograph while supporting more information in compatible analysis software. Conversely, the presence of a .jpg extension does not establish that every thermal-looking image contains reusable radiometric data. Confirm the actual saved format and the software's ability to read it.
Ask the supplier to provide a native file from the quoted configuration and a separately exported presentation image. Open both in the intended review software and record the difference in available functions. Do not infer radiometric capability from a screenshot of the camera display. A screenshot may show a spot value and palette but still lack the underlying data required for later review. The acceptance test should demonstrate the required information in the delivered file, not merely a similar-looking image on the supplier's computer.
Specify the camera and lens together
A camera's pixel count alone does not determine whether it can support the intended measurement task. FLIR's discussion of measurement distance and field of view explains the relationship between resolution, field of view and the target's representation in the image. Use that information to request an application review for the proposed camera and lens. Do not treat a high-resolution specification as proof that any target can be measured from any convenient position.
Provide the supplier with the relevant application conditions through the technical owner and ask for a documented response. Record the demonstrated lens, camera configuration and limitations. If an alternative lens is necessary for one task, include it in the quote and identify its role in the equipment record. A sample dataset from a different lens or camera should be labeled accordingly. It can illustrate the software, but it should not silently become evidence that the quoted package supports the same spatial measurement requirement.
Make original capture context part of the requirement
Determine which capture information the reviewer needs, including equipment identity, date and time, asset or location identifier, relevant measurement parameters and supporting observations. Ask the supplier which fields are stored in the native file and which require manual entry or a separate record. A temperature result without its necessary context can be difficult to assess later. The technical owner should define what must be retained; procurement should verify that the proposed workflow can retain it without relying on undocumented operator memory.
Distinguish automatically recorded values from user-entered values and later edits. Ask whether the software preserves original information when a reviewer changes an analysis parameter or adds a comment. If it does not, establish how the organization will retain the original file and document the derived version. The buying decision should include that record-management effort. A platform can be suitable even when some controls are procedural, but those controls should be explicit rather than inferred from a broad statement that the system supports reports.
Test the real transfer route with a representative file
A file that works directly from the camera may lose useful information when passed through another application. Evaluate the transfer route the organization actually intends to use: a supported cable connection, removable media, a managed upload or another approved mechanism. Use nonproduction demonstration data. Compare the received file with the original in compatible analysis software and confirm that the required information remains available. Do not assume that every application offering image sharing preserves measurement-specific data.
Document the exact steps used during the test and identify any operation that creates a presentation copy. An image pasted into a document or recompressed for a messaging workflow may serve communication needs without serving archival needs. The appropriate process can retain the original separately and link it to the report. What matters is that users know which artifact is authoritative for reanalysis. A convenient preview should not become the only surviving record simply because it is easier to open in a generic viewer.
Separate native records, analysis projects and issued reports
Ask the supplier to show the relationship between the camera file, an analysis project and the final report. Each can contain different information. The native file preserves the captured evidence; an analysis project may contain selected measurements and interpretations; a report presents a chosen result to a reader. Determine which artifacts the contract or internal process requires and how they remain linked. Avoid treating the ability to regenerate a colorful PDF as proof that the original measurement data have been retained.
Create a demonstration folder with clearly named originals, working analysis and issued outputs. Have a second person locate the source for one report image without guidance from the operator who created it. Record any ambiguity. If the report embeds only a flattened image, provide a stable reference to the native record through the approved document process. If the software can package the sources with the report, verify the contents and reader requirements rather than assuming that an export button includes every linked file.
Review how edits change the evidence
Analysis software may allow changes to palettes, measurement tools and other parameters. Ask which changes are presentation-only and which affect the reported measurement interpretation. The technical owner should determine permitted edits and review requirements. Procurement should demonstrate whether the system identifies the changed state and whether the original capture remains recoverable. A visually improved image can be useful, but the record needs enough context for another reviewer to understand what was changed after capture.
Use a fictional demonstration case in which the reviewer adds an area tool and creates a revised report. Check whether the earlier report, original file and revised analysis can be distinguished. Do not overwrite the original file merely to simplify the folder. If the software's normal save behavior changes it, decide how the organization will preserve an original copy through its controlled workflow. This evaluation addresses record integrity; it does not recommend altering parameters to obtain a preferred result or substitute for competent thermographic interpretation.
Preserve asset and location identity across repeat visits
Thermal surveys often revisit assets or locations. Ask how the package identifies a repeated inspection point and distinguishes it from a nearby component with a similar appearance. A timestamp and filename can identify a capture event, but they may not identify the asset in a way a future reviewer can reproduce. The required reference may include an asset number, route location, contextual photograph or another approved identifier. Determine what the workflow needs and how each item is captured and retained.
Test a small fictional route containing two similar assets and one repeat visit. Export the files and ask a reviewer to match them without relying on the order in which the images were taken. If the system offers route templates or reference images, confirm the included license and how changes are controlled. Do not assume those features exist in every camera or software tier. A simpler manual approach may be adequate if it preserves the required identity consistently and its effort is reflected in the purchase comparison.
Compare historical images without hiding context changes
A repeated image can look different because of a changed palette, view, operating condition or measurement context. Ask the technical owner what information is necessary for meaningful comparison and whether the software makes those differences visible. The buyer should not accept a demonstration that treats two visually different colors as sufficient evidence of a condition trend. The equipment and reporting package should support the context required by the actual analysis, including any accompanying observations maintained outside the image file.
Create a sample comparison record with the source filenames, capture identities, relevant context references and reviewer conclusion. Keep the original images available. If the software normalizes presentation settings for comparison, record that operation where the process requires it. The purpose is to make the basis of comparison inspectable. This guide does not define alarm thresholds or diagnose equipment from thermograms. It helps the purchaser ensure that the selected system can preserve the information the qualified reviewer needs to make those judgments.
Include offline review and long-term access in the quote
Ask whether the required analysis functions work without a live internet connection and what happens when a subscription or account changes. Obtain a response for the quoted license rather than the whole software family. If the organization must review records years later, determine how it will retain compatible software access or another approved readable form. A perpetual image archive and a time-limited analysis license are different commitments. Both should be visible in the commercial comparison when long-term review is required.
Request a handover test on a second workstation with the intended permissions and software edition. Confirm that it can open the native file, locate the required metadata and review the analysis or report. If a proprietary format is involved, identify the supplier's support and migration arrangements. Do not promise universal compatibility merely because the file is called JPEG. The record may contain a generally viewable image while its measurement component still depends on compatible software and the particular format implementation.
Work through a fictional flattened-image problem
A hypothetical inspection company evaluates a thermal camera and successfully opens a radiometric sample in the supplier's software. It then sends the image through its ordinary report-preparation application. The resulting exported picture looks identical, but the reviewer can no longer use the required measurement tools on that copy. The camera may still satisfy the requirement; the tested transfer route does not preserve the same artifact. The team records where the presentation copy was created and retains the native file through a separate approved path.
The revised workflow links the issued report to the original capture and saves the analysis project where required. A colleague repeats the handover test and confirms that the native record remains usable. This fictional example does not claim that any named application strips metadata or that every compression step has the same effect. It demonstrates why buyers should test their actual workflow. A successful camera demonstration alone cannot establish what a later document, sharing or archiving application will preserve.
Price the complete evidence workflow
Compare the camera, required lenses, batteries, accessories, calibration or service evidence, analysis software and storage arrangements as a package. Include the time needed for manual identity entry and report preparation where those tasks remain outside the software. Avoid estimating productivity from a single attractive image or a supplier-prepared report. A representative trial can reveal whether users can complete the required evidence package with the quoted tools and how much support the organization must provide.
Ask what happens after a lens replacement, camera repair or software update. Identify the records and review needed to preserve the approved configuration and reader compatibility. A service return should be connected to the affected camera and accessories rather than filed under a generic thermal kit name. Keep the original purchasing assumptions visible so later changes can be assessed against them. The equipment coordinator does not need to make thermographic judgments, but does need to know which configuration and documentation the technical owner accepted.
Define a practical file acceptance test
Before final acceptance, have the supplier or demonstration team create a nonproduction record with a known fictional asset identifier. Save the native file, transfer it through the intended route, open it on the receiving workstation and create the required report. Check that the expected measurement functions and context remain available and that the original can be distinguished from derived copies. Record the camera, lens, software versions and transfer path used. This is a purchasing acceptance exercise, not a substitute for technical qualification of the inspection method.
NDT Connect's free equipment tracker records asset details, calibration due dates, status and notes. It does not store thermal images, decode radiometric files, perform temperature analysis or manage inspection routes. Use the selected inspection and document systems for those records, with a concise evidence reference in the asset notes if appropriate. The purchase is ready for its authorized disposition when the complete record path has been demonstrated and any limitations have owners. That is stronger evidence than a thermal-looking JPEG that nobody has tried to reopen for its intended purpose.
Frequently Asked Questions
Does a JPG filename prove the image is radiometric?
No. Check the actual file from the quoted camera and transfer path in compatible analysis software. A normal image and a radiometric image may share the same extension.
Is a screenshot enough for later temperature analysis?
A screenshot can communicate a result, but it should not be assumed to preserve underlying radiometric information. Retain the required native record.
Can a report image replace the original thermal file?
Only if the applicable record requirements explicitly allow that deliverable. Test what the report preserves and maintain source links when native evidence is required.
References & Standards Cited
- FLIR T8xx manual: saving and working with radiometric images View source ↗
- FLIR: measurement distance, resolution and field of view View source ↗
Related on NDT Connect
Join NDT Connect — free
The free marketplace for the NDT industry — connect inspectors and the companies that need them.
Free to join · Compare provider qualifications and confirm availability directly · Browse providers
By NDT Connect Editorial · Updated
Source-based editorial guidance. Read our editorial policy and disclosures.