VuMark

Overview

A VuMark is Vuforia's customizable augmented-reality marker — described by Vuforia as "the next generation bar code" — that simultaneously encodes data and acts as a trackable AR target while allowing a fully branded, designer-controlled appearance [1, 2]. Unlike a plain square fiducial, a single VuMark design can be styled to match a company's brand or logo and then instanced to encode many different unique IDs or data values [1]. Like aruco and apriltag it recovers 6-DoF pose; unlike them it is a proprietary, design-driven format aimed at enterprise AR rather than robotics.

History

VuMark was introduced by PTC (which owns the Vuforia platform) with the Vuforia 6 release, announced January 28, 2016 as part of PTC bringing augmented reality to the enterprise [3]. Vuforia 6 introduced the VuMark as a customizable visual code that lets AR experiences be attached to any product or object [3].

Technical specification

VuMarks are authored from Scalable Vector Graphics (SVG) files uploaded to the Vuforia Target Manager, which generates trackable instances in PNG, PDF or SVG form [2]. A VuMark design is composed of several defined parts [2]:

• Contour — the implied outer closed path formed by the contrast between the Border and the Clear Space; it must consist of straight lines forming a closed path with at least 4 and at most 20 sides, and ideally is not rotationally symmetric (so orientation is unambiguous) [2].
• Border — typically the most identifiable, defining shape of the VuMark [2].
• Clear Space — a mandatory blank region adjacent to the Border along its entire length (inside or outside), guaranteeing enough contrast to detect the Contour [2].
• Code — the visual representation of the encoded ID, made of Elements; the number of Elements depends on the data type and value length [1]. Every Element must have a Bright and a Dark state, represented by two high-contrast colors [1].
• Background / Design Area — free design layer not used for detection, giving wide creative latitude [2].

Data and capacity. A VuMark instance can encode a unique identifier as a string, number (numeric), or bytes [1]. A single VuMark design can present millions of uniquely identifiable instances [1]. Detection finds the Contour, reads the Code Elements, decodes the ID, and uses the marker geometry to estimate the camera pose for AR overlay [1, 2].

Use cases

• Enterprise AR — scalable identification of objects with branded markers, overlaying 3D step-by-step instructions for maintenance and training [1].
• Product / serial encoding — encoding a URL or product serial number in a mark that does not detract from product appearance, across a product range sharing one visual design [1].
• Branded AR experiences — attaching AR content to logos, icons or packaging while preserving brand identity [1].

Comparison

Versus aruco and apriltag: those are open, austere black-and-white square grids optimized for robotics and maximum detection robustness; VuMark instead prioritizes brand-designable aesthetics and arbitrary shape (4–20-sided contours, custom colors and artwork) while still carrying an error-tolerant coded ID and supporting AR pose tracking [2]. VuMark's ID space (millions per design via string/numeric/byte payloads) exceeds the small fixed dictionaries of typical ArUco/AprilTag families [1]. The trade-off is that VuMark is proprietary to the Vuforia Engine, with no open detector library, whereas ArUco and AprilTag are open source.

Status

Active, proprietary. VuMark is a supported feature of the Vuforia Engine and authored via the Vuforia Target Manager / VuMark Designer; all license tiers allow developing and publishing with VuMarks [1].

Sources

1. VuMarks — Vuforia Engine Library (PTC), accessed 2026
2. VuMark Design Guide — Vuforia Engine Library (PTC), accessed 2026
3. PTC Brings Augmented Reality to the Enterprise with Vuforia — Business Wire, 2016

Deployments

No country reports mention this standard by name.

Regions / aggregations not mapped to a single country

• Universal