Chromperfect Knowledge & FAQ Hub
Your complete resource for Chromperfect — structured for clear, fast answers on installation, licensing, connectivity, data integrity, and regulatory compliance. Built for easy discovery by users and intelligent search systems alike, ensuring accurate, verified information is always within reach.
Configuration
Licensing
Communication
Automation
Sequences
Processing
Files
21CFR Part11
Compliance
Scalability
Performance
Files
Reports
Apps
Admin
Support
Upgrades
Features
OEM
Choose a category
What is the Chromperfect Method File Editor and what does each tab control?
Show answer
The Chromperfect Method File Editor is used to create and edit Method (.MET) files, which define how data is acquired, processed, plotted, and reported.
Each tab in the Method File Editor controls a specific part of this workflow. The Acquisition tab defines run time, sampling rate, and real-time plot behaviour. The Events tab defines timed events, including integration behaviour. The Processing tab controls how Raw files are processed, including peak detection, peak width, output files, and alignment. The Report, Plot, and Plot Options tabs control printed and saved report and plot appearance.
Additional tabs define user programs, units, SEC-specific behaviour, alignment, and documentation fields. Together, these tabs allow a Method file to fully define how chromatography data is handled from acquisition through final reporting.
For a full, tab-by-tab explanation, see the Chromperfect Method File Editor user training video and accompanying guide.
Reference Links
YouTube:
https://youtu.be/hp6Vyl1arCg
Blog:
https://www.chromperfect.com/post/chromperfect-method-file-editor-overview
Do I need to uninstall Chromperfect before upgrading?
Show answer
Yes. When upgrading Chromperfect on the same PC, the existing version must be uninstalled first using Windows Apps & Features or Add/Remove Programs. This is required by the Windows installer and is expected behavior.
Uninstalling the old version does not remove instrument configurations or user settings. Chromperfect preserves these during the uninstall so they can be reused by the new version.
After uninstalling, do not manually delete Chromperfect working or data directories unless you intentionally want a completely fresh installation and understand that all previous settings will be lost.
Check out the Blog post on the topic
https://www.chromperfect.com/post/upgrade-chromperfect-do-you-need-to-uninstall-the-existing-version-first
Are Chromatography PDF Reports the Same as Data Files?
Show answer
No. Chromatography PDF reports are report outputs, not data files.
In chromatography systems, the primary data is stored in RAW data files, which contain the full detector signal and all metadata required for reprocessing, reintegration, and audit traceability. PDF files are created from that data to present results in a readable, shareable format.
PDF reports cannot be used for further analysis and should never replace the original data files. Chromatography software may generate PDFs automatically, via batch processing, or through printer-based workflows, but in all cases the RAW data remains the authoritative record.
Our blog post explains this in greater depth
https://www.chromperfect.com/post/understanding-chromatography-pdf-reports-data-files-vs-report-outputs
Can baseline noise be measured in a Chromperfect report?
Show answer
Yes. Baseline noise can be measured and included in a Chromperfect report, but it is not calculated automatically.
In Chromperfect, noise is not a peak attribute and is not associated with retention time, area, height, or calculated amount. Instead, noise is a property of the chromatogram signal over a defined baseline region.
To measure noise, a user defines a baseline region and calculation inside a Format file. The resulting noise value is typically reported in the report header, footer, or summary section as a single run-level result.
This approach allows users to control where and how noise is measured, rather than relying on a fixed or hidden definition.
We have a blog post and video about this topic available from the link
https://www.chromperfect.com/post/how-to-measure-baseline-noise-in-chromatography-reports
How do I change the Chromperfect data acquisition directory?
Show answer
If your Raw data files are being saved in the wrong location, the Chromperfect data acquisition directory for that instrument has not been set correctly.
In Chromperfect, the data acquisition directory is configured per instrument and must be changed from the Selection tab in the Run program. The Status tab is view-only and cannot be used to modify this setting.
Once the correct directory is selected and saved, all new acquisitions for that instrument will be written to the chosen folder. For a full step-by-step walkthrough, see the related article and video.
https://www.chromperfect.com/post/how-to-change-the-data-acquisition-directory-in-chromperfect
How do I name or rename an instrument in Chromperfect?
Show answer
In Chromperfect, the instrument name is a user-defined text label used for identification only. It is not read from the instrument hardware and is not a dynamic value.
Instrument names are configured in the Connections dialog and are used throughout the software, including the data acquisition program, chromatogram plots, and report headers.
Renaming an instrument does not affect data acquisition, instrument communication, licenses, or existing data files.
For step-by-step instructions, see:
https://www.chromperfect.com/post/how-to-name-or-rename-an-instrument-in-chromperfect
Can I edit the Chromperfect .VER license file to change options or instruments?
Show answer
No. Chromperfect .VER license files must never be edited.
Although the license file can be opened in a text editor for viewing, it is a protected file. Any attempt to modify it — even a small change — will immediately corrupt the license and make it unusable.
The .VER file is not a configuration file and cannot be edited to add instruments, change options, or extend licensing. All licensing changes must be issued by Chromperfect and provided as a new license file.
What is the Chromperfect .VER license file?
Show answer
The .VER file is Chromperfect’s license file and contains the information that allows the software to run under a valid license.
For USB licenses, the USB key always contains the master copy of the license file. During installation, a working copy of this file is placed on the computer, typically in the Chromperfect program directory.
If licensing issues occur, they are often resolved by ensuring the correct .VER file is present and synchronized with the USB license key. The .VER file should always be copied from the USB key to the local Chromperfect directory if recovery is required.
Why does my USB license work on one PC but not another?
Show answer
In some Windows configurations, a USB license key may be assigned a drive letter that conflicts with system-reserved devices.
A common example is the USB key being assigned drive letter D:, which Windows often reserves for optical drives such as CD or DVD devices. When this happens, Chromperfect may not be able to reliably detect the license key.
Reassigning the USB license key to a different drive letter, typically E: or higher, usually resolves the issue. This change is made using Windows Disk Management and may require administrative privileges or assistance from IT support in managed environments.
Can Chromperfect licenses be used on virtual machines?
Show answer
Chromperfect licenses can be used in virtual environments, but the license type is important.
USB licenses are the recommended option for virtual machines. They are not tied to the underlying system configuration and are unaffected by common virtual machine operations such as snapshots, restores, or host migrations.
Fingerprint licenses are locked to the hardware environment of a single system. In virtual environments, that environment can change more easily, which may cause the license to no longer match the system. For this reason, fingerprint licenses are generally not recommended for virtual machines unless the environment is carefully controlled and remains static.
