This section is non-normative
SVG Native is a profile of SVG designed with the requirements of native apps. The environment native apps run in is different than the environment of Web browsers in a few fundamental ways:
Security: Web content is usually sandboxed, and has only a fraction of the capabilities that a native app has. One of the reasons for this sandboxing is to mitigate security risks that SVG content may contain. However, native apps are usually either not sandboxed or have a more permissive sandbox than Web content. Therefore, code that runs in a native app must be held to a higher standard of security.
Performance: Web content is usually run in a separate process, which means the performace of that process has only an indirect affect on the performance of the entire app. If this separate process stalls, the entire app can continue and gracefully degrade behavior. However, native code runs in the app’s process, which requires more stringent performance targets.
SVG Native aims to adhere to the native app environment by meeting the above requirements.
SVG Native also has one additional goal:
Ubiquity: SVG Native should be implementable as a system component on any modern computing environment. This means it should be small, lightweight, and only have few dependencies. The dependencies it does have should be standard components that already exist in most computing environments.
To meet these goals, SVG Native is a subset of SVG 1.1, which removes animation, interactivity, linking, remote resource loading, scripting, and CSS (among others).
1.1. Use Cases
This section is non-normative
SVG Native is designed to fit a number of use cases.
Icons: Icons are often small vector graphics containing few graphical elements.
Emoji: Emoji are often represented as small vector graphics.
Color Fonts: Each glyph in a font is represented as a series of vector contours. Color fonts allow the glyphs to include color, in addition to their contours.
Drawings and sketches: Drawings and sketches may be created with vector artwork tools. Depending on the complexity of the artwork, representing it using a series of vector drawing elements may result in a smaller file size than a raster format such as [PNG]. Drawings and sketches often need to be viewed outside of the Web platform.
SVG Native is presented as a series of modifications of the Secure Static Mode of [SVG2]. These modifications are applied as differences from that specification. Rather than being a strict line-by-line diff, this specification describes the differences directly.
If functionality present in [SVG2] isn’t present in the SVG Native specification, SVG Native includes that functionality.
There are numerous differences between the SVG Native format and the [SVG2] format. Currently, all differences are reductive; all functionality in SVG Native is also present in [SVG2]. A conforming SVG Native document must only include functionality present in the SVG Native format. A conforming SVG Native renderer should ignore any functionality requested by a document that is not present in the SVG Native format. If a SVG Native renderer intentionally chooses to honor functionality beyond the SVG Native specification, it must do so in accordance with the [SVG2] specification. There are a few exceptions to this throughout this specification below, where an SVG Native renderer must not include some functionality from [SVG2].
Note: If a document uses parts of SVG that aren’t part of SVG Native, then it isn’t a conformant SVG Native document. When an SVG Native renderer opens such a file, it should ignore all of those parts. Therefore, all SVG Native renderers should produce the same rendering for the same document. However, there may be renderers which intentionally decide to honor parts of SVG that aren’t part of SVG Native. In order to make it more likely that a given document’s rendering is predictable, even in these renderers, SVG Native authoring tools are recommended to always emit documents that conform to this specification. The SVG Working Group is considering producing a validator to determine whether a given document is conformant to the SVG Native format.
The file type and mime type is being discussed in this GitHub issue.
SVG Native is a standalone file type, expected to be rendered with a dedicated-purpose renderer. Therefore, SVG Native content must not be present as part of a larger XML (or HTML) document. If it is present as part of a larger XML (or HTML) document, the content should be interpreted as SVG proper.
Note: This means that browsers encounting a SVG Native root element within the DOM must not interpret it as SVG Native, even if it has the baseAttribute attribute set to
native. If a Web author desires to use SVG Native on the Web, the
img element may be used instead. This matches other native image formats such as [PNG]. A Web browser should implement SVG Native by linking with the system’s SVG Native facilities. This matches the implementation of other native image formats.
The root element of an SVG Native document must have the baseAttribute attribute set to
native and the version attribute set to
The file extension for SVG Native is
.svn. The UTI for SVG Native is
public.svg.native. The MIME type for SVG Native is
User agents may limit the reference depth of references to implementation-dependent maximas. However, this limit must be greater than or equal to 1 reference.
XSL Processing is not supported by SVG Native.
No namespaces other than xlink are supported inside an SVG Native document. From the xlink namespace, only href is supported.
A valid SVG Native document must not contain any of the external or internal XML DTD subset.
1.3. Common Attributes
SVG 2.0 defines sets of common attributes wich might apply to multiple elements. These sets of attributes are not supported by SVG Native:
conditional processing attributes
all core attributes except for id
global event attributes
document element event attributes
graphical event attributes
deprecated xlink attributes except for 'xlink:href'
1.4. SVG Modules
SVG Native is a subset of the content in the [SVG2] specification, and some associated modules. They are:
No other SVG modules are supported by SVG Native. This includes:
2. Rendering Model
SVG Native does not support masking.
The following attributes are not supported by SVG Native:
The scroll value on the overflow property behaves identically to hidden.
The clip-path attribute is not supported on a
clipPath element must have either exactly zero or exactly one child. Anything more than that is not supported by SVG Native.
The scroll and the auto values of the overflow property are not supported by SVG Native.
3. Document Structure
The root element must be an
svg element, and all other
svg elements are not supported by SVG Native.
Conditional processesing attributes and elements are not supported in SVG Native. These include the
metadata elements are not supported in SVG Native.
Elements in foreign namespaces are not supported in SVG Native. Attributes in foreign namespaces, except the xlink (
http://www.w3.org/1999/xlink) namespace, are not supported in SVG Native.
Because SVG Native is a subset of [SVG2]'s Secure Static mode, only
image elements which contain base64-encoded
data: URLs of [JPEG] or [PNG] images are supported. [APNG] images are be rendered without animation, using standard backward-compatibility with static [PNG] images. No other image format is supported by SVG Native.
All external resource loading is forbidden.
symbol element is not supported by SVG Native.
style element and the style attribute are not supported in SVG Native.
Note: Style properties can be set by presentation attributes, which must be parsed and processed according to the SVG and CSS specifications, other than the specific restrictions outlined in this section.
calc() is not supported by SVG Native.
env() and var() are supported by SVG Native.
Note: Because of the other restrictions on styling, there is no way to set new values to CSS custom properties inside an SVG Native document. However, some rendering environments (e.g., for SVG fonts) will expose custom property values from an external document, as if they were inherited by the root element of the SVG Native document; the `var()` function can therefore be used similar to the `env()` function, to access this value if it exists and set a fallback value if it doesn’t.
The CSS all property is not supported by SVG Native.
All the global CSS keywords are not supported by SVG Native. These include:
Percentage length values are not supported by SVG Native.
Relative units are not supported by SVG Native.
5. Geometry Properties
Keyword values, such as auto, are not supported in the cx, cy, r, rx, ry, x, y, width, and height attributes.
Note: Raw numbers are supported by these attributes, in accordance with the [SVG2] rules on parsing presentation attributes.
6. Coordinate Systems, Transformations, and Units
Only the following units are supported by SVG Native:
The transform property is only supported by SVG Native on the following elements:
The viewBox attribute is only supported by SVG Native on the
The preserveAspectRatio attribute is only supported by SVG Native on the following elements:
The pathLength attribute on the
path element is not supported by SVG Native.
All text and fonts facilities are not supported by SVG Native. This includes
font-face-name, inline-size, shape-inside, shape-subtract, shape-image-threshold, shape-margin, shape-padding, text-anchor, glyph-orientation-horizontal, glyph-orientation-vertical, kerning, text-overflow, 'xml:space', text-decoration-fill, text-decoration-stroke, letter-spacing, text-align, text-align-last, text-indent, word-spacing, white-space, vertical-align, dominant-baseline, alignment-baseline, baseline-shift, direction, text-orientation, writing-mode, font, font-family, font-feature-settings, font-kerning, font-size, font-size-adjust, font-stretch, font-style, font-variant, the subproperties of font-variant, font-weight, text-decoration, text-decoration-line, text-decoration-style, text-decoration-color, and text-rendering.
9. Embedded Content
HTML elements in SVG subtrees are not supported by SVG Native.
foreignObject is not supported by SVG Native.
10. Painting: Filling, Stroking, and Marker Symbols
The display attribute is not supported by SVG Native.
Note: Hiding elements can be achieved with the visibility attribute.
marker element is not supported by SVG Native, nor are the marker, marker-start, marker-mid, and marker-end properties.
The context-fill and context-stroke values are not supported by SVG Native.
Note: Authors wishing to use a contextual color from the environment may use currentColor.
color property is not supported by SVG Native.
Note: The absence of
color makes it impossible to change the value of currentColor from its initial value.
The vector-effect, paint-order, color-interpolation, and will-change attributs are not supported by SVG Native.
All color interpolation occurs in the sRGB color space.
11. Gradients and Patterns
Only the userSpaceOnUse value of gradientUnits is supported. According to [SVG2], the default value of gradientUnits is objectBoundingBox, which isn’t supported. This means that all
gradient elements must include
gradientUnits="userSpaceOnUse" to be valid.
pattern element is not supported by SVG Native.
12. Scripting and Interactivity
All scripting and interactivity facilities are not supported by SVG Native. This includes the pointer-events and zoomAndPan attributes and the
script element. No contents of the SVG Native document are focusable.
All external resource loading is forbidden. All URLs must either be a data URL or only consist of a fragment identifier.
a element and
view elements are not supported by SVG Native.