Turn a BLF from CANoe or a data logger into a readable ASC text trace, or a raw-frame CSV. CAN and CAN FD frames are kept as logged, and the file never leaves your browser.
Step 1 of 3 · Upload logs
Drop your BLF file here
or.blf files up to 150 MiB, up to 5 at a time. Conversion runs in your browser, so files stay on your computer.
A BLF is a binary container. These are the situations where a plain-text ASC trace is the better file.
date Wed Oct 21 10:42:03.123 2026
base hex timestamps absolute
internal events logged
Begin Triggerblock Wed Oct 21 10:42:03.123 2026
0.000000 Start of measurement
0.000000 1 1A0 Rx d 8 00 40 1F 00 01 00 00 00
0.010000 1 3E8 Rx d 8 11 22 33 44 55 66 77 88
0.020000 CANFD 1 Rx 18DAF110x 1 0 f 64 …ASC is plain text. Open it in any editor, search for an ID, or commit it to Git and compare two captures line by line.
% reads ASC, not BLF
data = canSignalImport('drive.asc',
'powertrain.dbc');Many scripts and importers read Vector's ASC layout rather than BLF. MATLAB's canSignalImport is one of them.
CANoe: Tools, Logging File Conversion
drive.blf → drive.asc
Here: no licence, nothing installedVector's own route is Tools, Logging File Conversion inside CANoe. This page does the same job with nothing installed.
$ grep ' 1 3E8 ' drive.asc | wc -l
105880
$ awk '$2==2' drive.asc | headOne frame per line means grep, awk or a few lines of Python are enough to pull out one ID or one channel.
Three steps, all in your browser.
Drop up to five BLF files. Each one is checked for readable CAN frames before you continue.
ASC is the default. Pick CSV for a table of raw frames, and rename the file if you like.
Each BLF becomes its own file with the same name. Nothing is uploaded at any point.
Frames are copied as logged. Nothing is decoded, so no DBC is needed.
date Wed Oct 21 10:42:03.123 2026
base hex timestamps absolute
internal events logged
Begin Triggerblock Wed Oct 21 10:42:03.123 2026
0.000000 Start of measurement
0.000000 1 1A0 Rx d 8 00 40 1F 00 01 00 00 00
0.010000 1 3E8 Rx d 8 11 22 33 44 55 66 77 88
0.020000 CANFD 1 Rx 18DAF110x 1 0 f 64 …The first lines of an ASC file written by this page, from the synthetic sample log.
A date header, base hex with absolute timestamps, then one line per frame: time, channel, ID, direction, length and data. 29-bit IDs end in x, and CAN FD frames use CANFD lines with BRS and ESI.
One row per frame: time, channel, ID, ID format, type, length and data bytes. Up to 2,000,000 frames per file.
CAN, CAN FD, remote and error frames, with channels numbered from 1 as in CANoe and timestamps counted from the first frame.
The BLF direction is not carried, so every frame is written as Rx. LIN, FlexRay and Ethernet objects are skipped. ASC has no public specification; the layout follows what CANoe and python-can write.
Yes. Choose the BLF, keep ASC selected and download the result. CANoe does the same under Tools, Logging File Conversion, but it needs a licence. This page needs nothing installed.
In your browser tab. The BLF is read and the ASC is written locally with no server involved, which suits logs from a prototype vehicle.
Yes. They are written as CANFD lines with up to 64 data bytes and the BRS and ESI flags. The bit-timing fields are written as zeros, the same way python-can does.
The converter does not carry the Tx or Rx direction from the BLF, so it writes Rx for every frame. If you need the direction, convert with CANoe instead.
The file follows the layout CANoe and python-can write, and this site's own ASC reader reads it back frame for frame. We have not tested every Vector version, so if a tool rejects a file, check its first lines against the example on this page.
Each BLF may be up to 150 MiB, and you can add five per run. One output file holds at most about 400 MB of ASC or 2,000,000 frames of CSV, so a larger capture needs splitting first.
Not on this page. It copies raw frames. To get decoded signal values as MAT or CSV, use the BLF to MAT converter, which maps a DBC to each channel.
The next job after this one, each on its own page.