Status: BarcoderX is under development and nothing is released yet. This page is a dated log, newest first, of what has been decided and built. Each change that affects what you will see or do adds a line here.
2026-11-21
The label service now tells browsers to use only https, by default. When a proxy that you list in network.trustedProxies says that the visitor used https, every answer carries Strict-Transport-Security: max-age=15552000 (six months, without includeSubDomains and without preload). It is never sent on plain http, and nothing is sent unless network.trustForwardedHeaders is on. If you already run the service behind such a proxy, this starts when you upgrade: browsers that see it will refuse plain http for that host name for six months. If that host may still need plain http, set network.sendStrictTransportSecurity to false before you upgrade. Your proxy must also write X-Forwarded-Proto itself. See The label service and Deploying the label service.
2026-11-20
A developer license is for one developer. There are no packs of 5 or 10: a team buys one developer license for each of its developers. Prices are on barcoderx.com. See Editions and licensing.
The USPS Facing Identification Mark and the USPS Intelligent Mail barcode can be encoded. The FIM takes one letter, A to E; a lowercase letter is read as uppercase. The Intelligent Mail barcode takes exactly 20, 25, 29 or 31 digits, and BarcoderX does not check the meaning of its fields. Neither takes options. This is built, not released, and the registry status is still Planned. See Postal barcodes: FIM and the Intelligent Mail barcode.
The two postal symbologies are drawn through the label engine in tests. Every FIM letter and an Intelligent Mail barcode of each accepted length render without a refusal, the bars land on the printer's dots, and bad data gives the same diagnostic codes as the encoder. See Postal barcodes: FIM and the Intelligent Mail barcode.
2026-11-19
A service without a license no longer refuses a label for the time that the evaluation mark takes. The mark is merged into the dots while the label is laid out, outside the layout's own time limit, so a request could be stopped with BX6007 for time that a licensed service does not spend. The time limit of a request (limits.renderMilliseconds) now counts from the end of the layout, and the wait that BX6006 and BX6015 give is the layout time and that limit together. See The label service.
2026-11-18
A picture of each element on its own, for the editor.POST /api/v1/render/elements takes a template and up to 64 element ids and gives back, for each id, a one-bit PNG picture cropped to the element, the box it takes (in the unit of the page and in dots), the size of the symbol of a barcode, the findings about the element and a hash that changes with everything that influences the picture, the evaluation mark included. An element that cannot be drawn on its own, or whose picture is too large, is reported without a picture and does not fail the request. Without a license the pictures carry the evaluation mark in their dots and the answer says so; the mark is a deterrent, not a lock. The limits are in GET /api/v1/meta/limits, and the .NET client has RenderElementsAsync. A request for elements takes more memory than a picture: with the default settings it takes two of the four places for drawing, and a caller may make 6 such requests a minute (rateLimit.elementRequestsPerMinutePerClient), so read Deploying the label service before you raise the number of requests. See The label service.
A release carries a signed release stamp, and a command checks it. The stamp holds the date of the build and the name of the release, signed by P4, so that the end of the updates window of a license can be judged against a date that P4 signed, not against the date of the computer. The command bx-license stamp verify --assembly <file> checks the stamp in a BarcoderX.Licensing.dll file and only reads the file. Its exit code says the result, and its messages say what to do. Until a release is stamped, a build has no stamp, and the command says so. See Evaluation mark and license keys.
UPC-E and the add-on symbols are drawn in a label, and a label that is accepted can be finished. The digits of an add-on now sit above the add-on's bars, level with the top of the main bars. The label engine also works out, before it draws, an upper bound of the work that the drawing needs, and refuses a label that is above the limit (BX3909, resource renderWork), so an accepted label is not stopped half way by the work limit. The digits of a barcode that shrink to fit are no longer counted twice. See UPC-E and add-on symbols and The label engine.
Two routes to check a template, and the printer commands as JSON.POST /api/v1/templates/validate returns every finding about a template, with the line and position of a problem in the text, in English or Spanish, and nothing is drawn or stored. POST /api/v1/templates/convert returns the canonical text of a template. The commands route answers with a JSON document (the commands and the notes of the engine) when the request says Accept: application/json; without it the answer is the plain text as before. See The label service.
Two more lists for the editor.GET /api/v1/meta/elements gives the element descriptors (labels as keys, no texts) and GET /api/v1/barcodes/symbologies gives the symbologies with their options and their names in English or Spanish; both have an ETag. GET /api/v1/meta/limits also gives the two limits that the descriptor bounds refer to. A service with a key gives a caller that has shown it more of the license state: the features, the finding codes and the next change. A refused request whose client resets within the second that the service spends on the rest of its body no longer makes the web server write an error line. See The label service.
The picture route is ready for the editor's 1-bit preview. A picture now carries its size in dots in BarcoderX-Image-Width and BarcoderX-Image-Height. A deployment for the web editor, which has a key and is not a public demo, may raise the template limit (limits.maxBodyBytes) up to 10 MB; a public demo keeps 262,144 bytes and refuses to start with more. Without a license, no request can get an unmarked picture. See The label service.
A slow sender no longer holds a place for drawing, and a refusal no longer keeps a connection. The service now reads the whole template, within 5 seconds (limits.bodyReadMilliseconds), before it takes a place for drawing; a caller that sends more slowly is stopped with the new code BX6017 (status 408). A refusal that is sent before the whole template has arrived is finished at once, and the connection is cut after one second if the rest has not come. Two codes were added, BX6017 and BX6018, so the page of diagnostic codes lists 207. The bodies being received have a budget of their own, a quarter of the memory budget of the renders. Deploying the label service says what the proxy still has to do. See The label service.
The label service answers three more questions for the editor.GET /api/v1/meta/licence says whether output is marked, GET /api/v1/printer-dialects and GET /api/v1/printer-profiles list the printer languages and the three generic ZPL profiles, in English or Spanish, with an ETag, so that a client receives the whole answer again only when something changed. The element and barcode lists come later. See The label service.
The label service is hardened for a public launch. A slow caller can no longer hold a place for drawing: the places are given back when the label is made, and an answer that waits for its reader waits in a pool of its own. Each caller has one request at a time and a limited number of connections. A broken body gets a plain 400 and no error in the log. A refusal says how long to wait, worked out from the limit that was reached. Two codes were added, BX6015 and BX6016, so the page of diagnostic codes lists 205. A new page, Deploying the label service, says what to put in front of the service and gives reference configurations for nginx and Caddy. See The label service.
2026-11-17
A label without a valid license is marked, and a license problem never stops it. BarcoderX now reads a signed license document on your own computer, with no network call, and works out whether a job is licensed, in evaluation, in a grace period or unlicensed. When there is no valid license for what a job uses, the output carries the evaluation mark: black badges with white words across the label, kept clear of barcodes where there is room so a scanner still reads them. The mark is a deterrent on pictures, not a lock. No license can be issued yet, so every picture is marked today. The new codes are BX9030 to BX9033. See Evaluation mark and license keys.
A template becomes a PNG file through the label service. The label service is a small program that you run yourself. You send it a template, and it answers with a PNG file in black and white, gray or color, or with a list of problems in English or Spanish. It stores nothing, and it limits the size of a request, the time it takes and how often a caller may ask. It is built, not released, the pictures carry the evaluation mark, and it is not for production use. See The label service.
The page of diagnostic codes lists 203 codes. The new ones are BX6000 to BX6014, the answers of the label service, BX9030 to BX9033 of licensing, and BX5130 to BX5133 of the ZPL composer, in English and Spanish. See Diagnostic codes.
The drawing of a label stays inside BarcoderX. The libraries below the engine are no longer public, and the engine no longer hands out its list of drawing steps. The one public way from a template to a picture is the engine and the PNG renderer that takes its whole result. Nothing can be drawn without passing through the engine. See The label engine and PNG output.
The rule from a length to printer dots is written down. A millimeter is exactly 1/25.4 inch, so it is not 8 dots at 203 dots per inch but about 7.99. Every edge is rounded to the nearest dot, and a half goes away from zero. See The label engine.
How big a barcode is. The page on barcodes now explains the two sizing modes, fixed and fit, and the template format page lists every member of a barcode. See Barcodes.
The label engine makes the drawing of a label. Given a template and a printer resolution, it works out the size of the label in dots, lays out the text, boxes and barcodes, and gives back a list of drawing steps. Anything that it cannot draw yet is left out, and a message says what and where. Digits under a barcode that are wider than their space are made smaller, down to 70 percent of the size asked for, before a warning is given. A label that cannot be made gives no drawing at all, never a half label. This is built, not released. See The label engine.
A label can be drawn and saved as a PNG file. The picture can be black and white for a printer, gray, or color for a screen. A label that is too large, a resolution that makes no sense or a file that would be too big is refused with a message that says what to change, and nothing partial is ever returned. This is built, not released. See PNG output.
A first ZPL writer sends a whole label to the printer as a picture. It has a plain form and a compressed form. The compressed form is off by default, because it has not been verified on a physical printer. This is built, not released. See ZPL output.
UPC-E and the add-on symbols can be encoded. The add-ons have two or five digits and go with an EAN-13, a UPC-A or a UPC-E. Add-ons for an EAN-8 are not built; they wait for the ISO/IEC 15420 standard. This is built, not released. See UPC-E and add-on symbols.
The page of diagnostic codes grew. It now covers drawing a label as a picture (BX3700 to BX3708), the label engine (BX3900 to BX3915), the number that cannot be shortened to a UPC-E (BX4022) and the ZPL writer (BX5101 to BX5121), in English and Spanish. It also says where to write when a message tells you to contact support. See Diagnostic codes.
A template becomes ZPL commands, and the web service can return them. The ZPL writer is now joined to the label engine. The label that the engine makes goes through a composer that draws it as the black-and-white picture and writes it as the commands of one label, and the small stateless web service returns them at POST /api/v1/commands?dialect=zpl. The commands carry the evaluation mark while no license is registered, and no license identity is ever written in them. The whole label is sent as one picture, with a notice (BX5130), because the printer's own text and barcode commands are not built yet. No commands have been run on a physical printer yet. See ZPL output.
These parts are joined in the small label service. The label engine, the part that draws and saves a PNG file and the ZPL writer meet in the stateless label service, which a program can call over HTTP. There is no released package and no public interface to call the libraries below the engine. The one public way to produce a picture or printer commands takes a label that the licensed engine made, and nothing else.
Notes for developers who host BarcoderX. Draw the result of the label engine only with the PNG renderer, which returns no picture when the drawing does not finish. Pass a time limit to every render. Cap how many templates are read and how many labels are drawn at once. A message carries names that were written in the template, so insert it into a page as text and neutralize line breaks before you write it to a log. Encode the canonical text of a template before you embed it in a page. A ZPL label that was refused or canceled can leave a format that was started and not closed, so never send it. See The label engine, PNG output, ZPL output and Diagnostic codes.
A correction. The pages on drawing shapes and on PNG output said that the label engine was not built yet. Its first part is now built, and the pages say what is still missing.
2026-11-15
The label template format can be read and written. BarcoderX reads a template written in JSON and refuses a damaged, oversized or hostile one with a code that says what is wrong and where. It writes a template back in one fixed form, so the same label always gives the same text. This is built, not released. See The label template format.
Text that reads from left to right can be laid out, and BarcoderX has its own typeface. Lines break at spaces and at line breaks, and text can be aligned, spaced and shrunk to fit its box. The built-in typeface BX Core, in regular and bold, covers English and Spanish letters, digits and the usual punctuation. Justified text, text that reads from right to left, kerning, italic and the other Western European letters are planned. This is built, not released. See Text on a label.
The drawing engine now draws outlines, blends and clips. Lines and the outlines of shapes can have a width, corners and line ends of your choice. Drawing can be limited to a clip area, and a list of drawing steps can be run on a color, gray or black-and-white surface. Dashed lines and pictures are not built yet. See Drawing shapes.
ITF-14, GS1-128 and SSCC-18 can be encoded. BarcoderX adds or checks the check digit, draws bearer bars for ITF-14, and reports the ratio of wide to narrow bars that a printer's whole dots allow. The list of GS1 identifiers is planned. This is built, not released. See Shipping barcodes: ITF-14, GS1-128 and SSCC-18.
The diagnostic codes are listed for the label model, drawing, pictures, fonts, text and barcodes. The page now has the title and explanation of each code in English and Spanish. See Diagnostic codes.
A correction in font support. A font whose tables are listed out of order, or whose character map lacks its closing entry, is rejected. The page used to say that such a font was used with a warning. See Font support.
These parts are not released on their own. They are libraries inside the engine that is still being built. There is no released package and no public interface to call them directly. The licensed engine will be the only public way to produce output.
Notes for developers who host BarcoderX. The canonical text of a template is not escaped for HTML. A message can contain words from a template, line breaks included. Reading a large template uses a lot of memory. A template that reads can still be too large to save, so check it when it is uploaded. See The label template format and Diagnostic codes.
Online activation and a periodic check-in are planned for licenses. BarcoderX sends no label, template, data or print job out of your environment. The one exception is licensing: activation and the periodic check-in send the license ID, a hashed machine fingerprint and the version, and they never block output. Sites with no network activate with a file. BarcoderX keeps a record of your activations: the license ID, the hashed fingerprint, the version and the time. See Evaluation mark and license keys.
A free online playground is planned. On barcoderx.com you will be able to try BarcoderX in the browser before you download anything: compose a small label, see it drawn and see the printer commands. It is a demonstration, not a service to depend on. Everything it draws carries the evaluation mark, and nothing you enter is stored. It comes after the first end-to-end version of the engine exists.
Artistic QR codes and decorated barcodes are planned for release 1.0, for the symbologies in that release. Decoration of linear symbols is in Basic, and decoration of 2D symbols is in Ultimate. See Barcodes.
The samples repository has an index. The public samples repository now lists ten topics, each marked Planned, with a short README for each topic in English and Spanish. The sample code in it is released under the MIT License; the BarcoderX SDK is licensed separately. See Samples.
Release 1.0 ships the first family of 50 symbologies. More families are planned after release 1.0. See Barcodes.
A page of diagnostic codes. The codes that BarcoderX has registered so far, with their title and explanation in English and Spanish, are listed in Diagnostic codes.
The Unicode version is fixed at 18.0.0. Right-to-left text and line breaking are planned and not built yet. The Unicode data files and test files of that version are part of the build and are checked on every change. See Text, fonts and pictures.
Font support is built, not released. BarcoderX can open and check a TrueType font file, and tells you why it rejects a file. See Font support.
The core of the drawing engine is built, not released. BarcoderX can work out what a filled shape covers, with curves, rotation and two fill rules. See Drawing shapes.
PNG output is built, not released. BarcoderX can write a PNG file from the pixels of a picture. After a .NET update the bytes of a PNG file can change while the picture stays the same, so compare pixels, not bytes. See PNG output.
This guide uses US English. Pages in English now use US spelling, such as "license" and "color". The web address of the page about evaluation and license keys has not changed.
2026-11-14
BarcoderX is software that you run yourself. BarcoderX is a toolkit for developers. You run the SDK, the API server, the editor packages and the print agent on your own infrastructure, and you buy licenses for them. Nothing is hosted for you. BarcoderX keeps only your developer account, your license keys and the versions you may download. An online service that BarcoderX runs for you is not part of the plan. See How the pieces fit and Editions and licensing.
Editor details. The label editor does not save user preferences. Opening a template from a web address is not in the first release. See The label editor.
This guide is brought up to date. It now describes each part of BarcoderX, what is available today (nothing to download yet), and what is planned, in English and Spanish. From now on, every change that affects users updates this guide in the same step.
2026-11-13
The label editor is a JavaScript product. The editor is written once, in TypeScript, and delivered as packages for React, Angular and Vue, with a .NET wrapper for Blazor and other .NET applications. This replaces the earlier plan for an editor written in Blazor, so that web developers can use the editor as a normal package in the framework they already know. See The label editor.
Editions, updates and the license model are decided. There are two editions of the SDK and the server, Basic and Ultimate, and one edition of the editor add-on. A license is perpetual and includes two years of updates and support. Renewal is optional and adds a year. OEM licenses come for 1, 5 or unlimited developers. Evaluation is free and its output is marked. Prices are on barcoderx.com. See Editions and licensing.
GS1 is a product goal. BarcoderX is designed to meet GS1's readiness criteria for 2D barcodes, for creating labels and for printing them. It will check GS1 Digital Link addresses and the sizing of 2D symbols for retail point of sale. See GS1 support.
More features were added to the plan. Among them: more length units, non-printing guides on the page, text overflow and input rules, printing jobs with several label sets, RFID passwords and locks, EPS export, thumbnails, template archives, a one-call barcode renderer, and display packages for barcodes in ASP.NET Core and Blazor pages. See Templates and data, Output formats and Barcodes.
The code base and its automatic checks are in place. The project builds, and checks run on every change, on Windows x64, Linux x64 and Linux arm64. They confirm that BarcoderX contains only code written for the project, the .NET platform and a short list of approved components, that the interface text exists in both English and Spanish, that nothing is hard-coded, and that the interface stays light only. The code base does not contain features that you can use yet.
The user documentation is published in English and Spanish, as a first overview page.