Convert LZ4 to MD

Turn LZ4 archives into Markdown. The LZ4 layer is removed and the bytes inside are written as they were.

Converted in an isolated sandbox on our serversDeleted after 24 hours

Drop LZ4 files on the dialor turn it to pick what to do

The text inside, without the LZ4 layer.The LZ4 wrapper comes off and the Markdown inside is written as it was.

  1. What you get

    One Markdown file. The LZ4 layer is removed, and the bytes inside are written out exactly as they were stored, with no changes to the text.

  2. What you need to ask for

    Ask for the format you know is inside the LZ4 file. If the file holds Markdown, choose MD. Any other target is refused.

    This conversion only unwraps. It does not turn other content into Markdown.

  3. When it stops

    The conversion stops with input_corrupted when the file could not be parsed as LZ4.

    It stops with unsupported_elements when the file holds something the target cannot carry, or when some inputs cannot become the format the join takes.

  4. Going the other way

    To pack a Markdown file back into LZ4, use MD to LZ4. There are no options to set for this conversion.

LZ4 and MD.What each format is.

The formats

From · LZ4

LZ4

A single file compressed with LZ4, built for speed over ratio.

Extensions
.lz4
MIME type
application/x-lz4
Kind
Archives
To · MD

Markdown

Plain text with light markup for headings, lists, links and code. What agents and developers write in.

Extensions
.md .markdown .mdown
MIME type
text/markdown
Kind
Text and data

In your code.The same LZ4 to MD conversion through the API, for your app or your agent.

terminal
$ cv convert archive.lz4 archive.md
$ cv convert archive.lz4 archive.md

Questions.What people ask about LZ4 to MD.

01OF 04

No. The bytes inside the LZ4 file are written as they were.

No. Ask for the format you know is inside. Anything else is refused.

The file could not be parsed. The conversion stops with that code.

One file.

More conversions.Other ways in and out of LZ4 and MD.