FlexLM / FlexNet Publisher
Shifts TIMESTAMP-based debug logs and time-only event rows by inferring dates from the current log context.
Browser-based license log utility
Log Timezone Shifting Tool
Shift license manager log timestamps from one timezone to another before analysis, sharing, troubleshooting, or combining logs from multiple regions.
Your log file stays in your browser. The tool creates a timezone-shifted copy for download and does not change the original file.
Timezone shifting tool
Upload a license log
Choose a supported license manager log, select the source timezone and target timezone, then download a shifted copy.
Drag and drop your log file here, or choose a file
Supported examples include FlexLM, RLM, Sentinel RMS, DSLS, Altair ALM, LM-X, .log, .txt, .dat, and vendor-generated license usage logs.
No file selected
Choose a log file to begin.
Auto-detect works for most logs. If the result looks wrong, choose the date format used in your log file.
Shifting log timestamps
The tool is processing the log in your browser and preparing a downloadable copy.
Timezone-shifted log file ready
Download the shifted copy and upload it to License Log Analysis, share it with a teammate, or keep it with your audit notes.
Download shifted log fileTimezone shifting summary
Supported license manager log types
Designed for common engineering license logs
The tool recognizes common timestamp styles used by supported license managers and keeps the rest of each log line unchanged.
Reprise RLM
Shifts standard report logs with full dates and detailed logs that use START dates with month/day event timestamps.
Sentinel RMS
Shifts month-name timestamp lines while preserving the surrounding usage, release, and denial event text.
Dassault Syst?mes DSLS
Shifts DSLS server log timestamps that start with year, month, day, time, and millisecond values.
Altair ALM
Shifts transactional usage rows that begin with a timestamp column before the remaining comma-separated details.
X-Formation LM-X
Shifts LM-X log records that include a Timestamp field with a date and time value.
What gets changed?
The tool changes detected timestamp values only. It does not translate, anonymize, reorder, merge, split, or recalculate license activity.
- Vendor names stay unchanged.
- Feature names stay unchanged.
- Users and workstation values stay unchanged.
- Denial reasons and original event text stay unchanged.
When should I use it?
Use timezone shifting when logs were generated in a different region than the team reviewing the data, or before comparing files from multiple license servers.
- Normalize logs before analysis.
- Prepare files for regional review.
- Align timestamps before sharing with support teams.
- Keep an unchanged original log for audit purposes.
Timezone conversion changes displayed log times, not license activity
Timezone shifting is a formatting transformation. It does not modify the underlying meaning of checkouts, checkins, denials, sessions, users, features, or quantities. Keep the original log file whenever you need an audit trail.
Daylight saving time is handled through the browser's timezone database. If the selected source and target timezones are the same, the output should keep the same displayed times.
Ready to analyze the shifted copy?
Turn timezone-aligned logs into clear reports
After shifting timestamps, upload the copied log to License Log Analysis to review usage, denials, sessions, active users, heatmaps, feature profiles, and utilization.