Extract text from MAVLink and MSBuild files (TLOG)
To convert TLOG log files to another format, you need Mission Planner or other Data software.
To convert other file formats to the "Telemetry and Transaction Log" file type, you need software like Mission Planner or a similar tool.
A .TLOG file is typically a MAVLink Telemetry Log generated by drone flight controllers or a Tracker Log from Microsoft Visual Studio MSBuild. For drones, the file records live telemetry data over a MAVLink connection, capturing flight metrics like GPS position, altitude, and sensor health. Software like Mission Planner is required to replay the flight or view the data. For developers, a .TLOG file tracks file read and write operations during the software build process, often encoded in UTF-16 LE. Other systems, like Alibaba's TLog framework, Elasticsearch, and Bitronix, use .TLOG extensions to store internal transaction and debug data.
The main disadvantage of the .TLOG format is its application-specific encoding. A telemetry log contains binary or highly structured data streams that standard text editors cannot parse. This means users cannot easily graph the data, share it with non-technical stakeholders, or analyze it in spreadsheet software. Similarly, transaction logs from different databases or software suites require the original environment to decode proprietary timestamps and event strings.
To make the data usable, you must convert the .TLOG file. For drone logs, converting to CSV allows for custom data analysis in Excel, while exporting to KML enables flight path visualization in Google Earth. For text-based tracker logs, converting the UTF-16 encoding to standard TXT or XML ensures compatibility with basic scripts and log viewers. Because these files vary heavily depending on the source application, standard online converters often fail to process them. Often, only the original software can properly read or export the data. Our platform can inspect the file, identify whether it is a drone telemetry log or a developer tracker file, and attempt to extract readable text. If our analysis detects a supported underlying or embedded format, viewing or conversion may still be possible.
Convert.Guru analyzes your TLOG file, detects the exact format, and lets you read the text inside.
Users also converted LOG, JSON, EDB, B01, INP, DAT, OCX, PRI, DTD, CSV and BIN files.
If you want to convert TLOG file to CSV, BIN, SYS, DLL, EXE, DRV, VXD, 386, COM, BAT, CMD or SCR, you can use Mission Planner or similar software from the "Log and Telemetry Data Storage" category. In the File menu, look for Save As… or Export….
To convert MSI, EXE, REG, MST, LNK, CAB, CAT, DRV, INF, SYS, MSU or DLL files to TLOG, try Mission Planner or another comparable tool in the "Log and Telemetry Data Storage" category.
The history of Convert.Guru began over 25 years ago in California with Tom Simondi’s file-format database. A former contributor to Space Shuttle development and a software pioneer of the 1980s, Simondi established a trusted resource for file type analysis that was even referenced by Microsoft Windows XP. Today, we use modern technology to process and convert thousands of file formats while continually improving our TLOG converter.