Read the QR codes and barcodes of an image inside the plugin runtime, with the open-source QR Code & Barcode Scanner engine. Returns the decoded texts and the engine's JSON report.
Choose an AI assistant to explain this destination using its public sources. Gemini opens gemini.google.com. Gemini, Copilot, DeepSeek, Meta AI and Qwen require pasting the prompt below; the other links include it in their URL. Sign-in or a manual paste may still be required. Check the answer against the documentation.
Use the code block's copy control, or select its complete text, then paste it into your assistant.
A Dify tool plugin that reads every QR code and barcode in an image file. Give it the image a user uploads, and the next step gets the decoded texts and the engine's report. The open-source engine runs inside your Dify plugin runtime: the image goes to no other service, and no model or key is needed.
The QR code scanner and the barcode scanner are QR Code AI's scanning pages in the browser. This plugin follows the same route as the QR code scanner Dify guide and the barcode scanner Dify guide. If a page is not online yet, this README is the reference.
To make a test image with a known value, use the QR code generator or the barcode generator. Keep the text you encoded with the image, then compare it with the the tool returns, character for character.
The plugin is built and tested in the engine repository. Its own repository,
,
has been public since 20 November 2026, and its tests pass there. It is not on the Dify Marketplace
yet.
Once the plugin is listed, install QR Code & Barcode Scanner from the Marketplace: in Dify,
open Plugins, then Marketplace, and search for it.
A package file installs the same plugin without the Marketplace. The Dify plugin command line,
, builds it from this folder:
The command writes a file. In Dify, choose Plugins, Install plugin, Local
package file and select it. Dify then installs the plugin's two dependencies,
0.11.1 and the engine wheel
0.11.0. The
command line is a program of the
Dify plugin daemon, not an npm or
PyPI package. The package has not been built in this repository.
A self-hosted Dify accepts only packages signed by the Marketplace by default. To install a local
package there, its administrator adds to and
restarts Dify.
The plugin has one tool, Scan QR codes and barcodes ():
The tool returns a one-line summary such as
, the engine's JSON report,
and three variables: (the decoded texts), and . is false when
the time budget cut the scan. A file the engine refuses makes the tool fail with the engine's
code, so a workflow can send it to its failure branch.
To try the plugin against a Dify instance before packaging it, write a file in this folder
with , set to the debugging address and
set to the key that Dify shows under Plugins, then run .
Never commit that file: the key opens your Dify workspace to the plugin.
is a draft of a
Marketplace template, Uploaded Image QR and Barcode Reader: a workflow app with no model that
sends found codes, an image with no code and an unreadable file down three branches.
holds its listing text and the steps that remain.
It has not been imported into Dify yet, and it waits for the plugin to be on the Marketplace.
The tests load the plugin with the Dify SDK, as the plugin runtime does at start, and call the
tool's with files served over HTTP:
They scan the sample in the three profiles and cover the defaults, an image with no code, a file
that is not an image, every size limit, bad options and a cut budget. They check the manifest
against the plugin daemon's rules and the template against the tool it uses. The workflow
of the engine repository runs them. They have not run inside a Dify
instance.
A Dify plugin lives at the root of its repository, so the plugin is served from a repository of its
own, . Nothing there is edited by hand.
writes its whole tree from one commit of the engine repository: this folder, the workflow of
, the two test images, the licence and a that names the commit
and the sha256 of every file. The same program checks that a tree is exactly that.
Dify gives the tool the uploaded file. The tool downloads it from Dify's file service and passes its bytes to the engine, which runs in the plugin's Python process and returns one report.
The picture is a recorded scan of the sample image, which holds a QR code and a Code 128 barcode.
Both come back in one report, each with its format, its exact text and the place where the engine
measured it: and .
The tool returns the summary text, the report as JSON and the , and variables. The JSON message is the engine's report, unchanged.
The report itself is described field by field in the
report reference.
An empty list of detections means the image holds no code the engine could read. A refused file
is an error with a code instead, listed in the
error codes.
The tool reads what the engine reads, from PNG, JPEG, WebP and GIF files. Codes of different formats in one image come back in one report. The engine's
supported formats
section states the known limits.
The Rust, Node.js, browser and Python packages hold the engine. The Go and PHP packages hold no decoder:
each one starts and hands you its report.
Language and platform names and logos belong to their owners. They identify a runtime or a destination and imply no endorsement.
Project-authored plugin source is MIT; see LICENSE. The plugin installs the engine wheel 0.11.0 from PyPI and does not ship it. The published engine 0.11.0 keeps the license it shipped with, AGPL-3.0-or-later; read the license packaged with the version you install and the licensing guide.
Maintained by Thibaut Mélen & Nicolas Cella for QR Code AI, a product of SuperNovae Studio. The license of each component is stated in its own license files.
Project-authored scanner code and documentation in this checkout are available under the MIT License. You may use, modify and redistribute this source in open-source or proprietary applications, including commercial products, while preserving the copyright and permission notice. Thibaut Mélen & Nicolas Cella develop QR Code AI at SuperNovae Studio.
Retained third-party code, dependencies, artwork and test data keep their own licenses and notices. The licensing guide explains these component boundaries; the project license does not assign a license to an unrelated platform or service.
Published archives retain the license shipped with their version. A pinned engine, adapter or bundle may therefore have different terms from this working source. Read its packaged license and the license history before reuse. The source change does not replace an archive or publish a new version.
No outbound calls found
Last checked 11/22/2026 09:07 AM · version 0.1.0