base on JPEG XL image format reference implementation # JPEG XL reference implementation []( https://github.com/libjxl/libjxl/actions/workflows/build_test.yml) []( https://github.com/libjxl/libjxl/actions/workflows/build_test_cross.yml) []( https://github.com/libjxl/libjxl/actions/workflows/conformance.yml) []( https://github.com/libjxl/libjxl/actions/workflows/fuzz.yml) []( https://github.com/libjxl/libjxl/actions/workflows/release.yaml) []( https://libjxl.readthedocs.io/en/latest/?badge=latest) []( https://www.bestpractices.dev/projects/7845) []( https://securityscorecards.dev/viewer/?uri=github.com/libjxl/libjxl) []( https://codecov.io/gh/libjxl/libjxl) <img src="doc/jxl.svg" width="100" align="right" alt="JXL logo"> This repository contains a reference implementation of JPEG XL (encoder and decoder), called `libjxl`. This software library is [used by many applications that support JPEG XL](doc/software_support.md). JPEG XL was standardized in 2022 as [ISO/IEC 18181](https://jpeg.org/jpegxl/workplan.html). The [core codestream](doc/format_overview.md#codestream-features) is specified in 18181-1, the [file format](doc/format_overview.md#file-format-features) in 18181-2. [Decoder conformance](https://github.com/libjxl/conformance) is defined in 18181-3, and 18181-4 is the [reference software](https://github.com/libjxl/libjxl). The library API, command line options, and tools in this repository are subject to change, however files encoded with `cjxl` conform to the JPEG XL specification and can be decoded with current and future `djxl` decoders or the `libjxl` decoding library. ## Installation In most Linux distributions, installing `libjxl` is just a matter of using the package management system. For example in Debian-based distributions: `apt install libjxl-tools` will install `cjxl` and `djxl` and other tools like `benchmark_xl` are available in the package `libjxl-devtools`. On MacOS, you can use [Homebrew](https://brew.sh/): `brew install jpeg-xl`. [](https://repology.org/project/libjxl/versions) From the [releases page](https://github.com/libjxl/libjxl/releases/) the following can be downloaded: - Windows binaries - Debian and Ubuntu .deb packages Of course you can also [build libjxl from sources](BUILDING.md). ## Usage To encode a source image to JPEG XL with default settings: ```bash cjxl input.png output.jxl ``` The desired visual fidelity can be selected using the `--distance` parameter (in units of just-noticeable difference, where 0 is lossless and the most useful lossy range is 0.5 .. 3.0), or using `--quality` (on a scale from 0 to 100, roughly matching libjpeg). The [encode effort](doc/encode_effort.md) can be selected using the `--effort` parameter. For more settings run `cjxl --help` or for a full list of options run `cjxl -v -v --help`. To decode a JPEG XL file run: ```bash djxl input.jxl output.png ``` When possible, `cjxl`/`djxl` are able to read/write the following image formats: OpenEXR (`.exr`), GIF (`.gif`), JPEG (`.jpg`/`.jpeg`), NetPBM (`.pam`/`.pgm`/`.ppm`), Portable FloatMap (`.pfm`), PGX Test Format (`.pgx`), Portable Network Graphics (`.png`), Animated PNG (`.png`/`.apng`), and JPEG XL itself (`.jxl`). Specifically for JPEG files, the default `cjxl` behavior is to apply lossless recompression and the default `djxl` behavior is to reconstruct the original JPEG file (when the extension of the output file is `.jpg`). ### Benchmarking For speed benchmarks on single images in single or multi-threaded decoding `djxl` can print decoding speed information. See `djxl --help` for details on the decoding options and note that the output image is optional for benchmarking purposes. For more comprehensive benchmarking options, see the [benchmarking guide](doc/benchmarking.md). ### Library API Besides the `libjxl` library [API documentation](https://libjxl.readthedocs.io/en/latest/), there are [example applications](examples/) and [plugins](plugins/) that can be used as a reference or starting point for developers who wish to integrate `libjxl` in their project. ## License This software is available under a 3-clause BSD license which can be found in the [LICENSE](LICENSE) file, with an "Additional IP Rights Grant" as outlined in the [PATENTS](PATENTS) file. Please note that the PATENTS file only mentions Google since Google is the legal entity receiving the Contributor License Agreements (CLA) from all contributors to the JPEG XL Project, including the initial main contributors to the JPEG XL format: Cloudinary and Google. ## Additional documentation ### Codec description * [JPEG XL Format Overview](doc/format_overview.md) * [Introductory paper](https://www.spiedigitallibrary.org/proceedings/Download?fullDOI=10.1117%2F12.2529237) (open-access) * [XL Overview](doc/xl_overview.md) - a brief introduction to the source code modules * [JPEG XL white paper](https://ds.jpeg.org/whitepapers/jpeg-xl-whitepaper.pdf) * [JPEG XL official website](https://jpeg.org/jpegxl) * [JPEG XL community website](https://jpegxl.info) ### Development process * [More information on testing/build options](doc/building_and_testing.md) * [Git guide for JPEG XL](doc/developing_in_github.md) - for developers * [Fuzzing](doc/fuzzing.md) - for developers * [Building Web Assembly artifacts](doc/building_wasm.md) * [Test coverage on Codecov.io](https://app.codecov.io/gh/libjxl/libjxl) - for developers * [libjxl documentation on readthedocs.io](https://libjxl.readthedocs.io/) * The development of jpegli, the improved JPEG encoder and decoder, will continue at https://github.com/google/jpegli ### Contact If you encounter a bug or other issue with the software, please open an Issue here. There is a [subreddit about JPEG XL](https://www.reddit.com/r/jpegxl/), and informal chatting with developers and early adopters of `libjxl` can be done on the [JPEG XL Discord server](https://discord.gg/DqkQgDRTFu). ", Assign "at most 3 tags" to the expected json: {"id":"7551","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"