xaml.to.designDocs

xaml.to.design docs

Last updated

What it is

xaml.to.design converts XAML files (.xaml) into editable Figma designs, through a Figma plugin.

OptionOutput
Figma pluginEditable Figma layers

The plugin requires Figma open. Full output details in the Output section below.

What it does

Drop in a .xaml. xaml.to.design reads the markup — shapes and geometries, brushes, transforms, clipping, effects, text, panels and controls — and lays it out as an HTML page, then rebuilds that page as native Figma layers, the way html.to.design imports a web page. The whole file comes in as one frame.

Where it runs

The plugin runs inside Figma — you'll need Figma open to use it (Figma Community). It runs in Figma design files, FigJam, Figma Slides and Figma Buzz.

The conversion itself runs on the ‹div›RIOTS API: the plugin sends the file there, then places the result on your canvas.

Supported input formats

FormatExtension
XAML (Extensible Application Markup Language).xaml

The root can be a drawing (a Canvas, a Viewbox, a Path) or a screen (a Page, a Grid, a StackPanel…). The file must be well-formed XML.

Output

The plugin imports the file into Figma as fully editable layers, in one frame named after the file. There is no import dialog: a XAML file is one drawing, with nothing to choose, so the import starts as soon as the file is dropped. On the free tier the frame comes in a parent frame, with a short rating card beside it.

Editability

ElementBehavior
ShapesPath, Rectangle, Ellipse, Line, Polyline and Polygon stay editable vectors, with their fills, strokes, dashes, caps and joins.
GeometriesPath data and PathGeometry, RectangleGeometry, EllipseGeometry, LineGeometry and GeometryGroup, with their fill rule.
TransformsRotate, scale, translate, skew and matrix transforms, around their RenderTransformOrigin.
BrushesSolid color, linear and radial gradient brushes become fills and strokes; opacity and opacity masks come across.
ClippingA Clip geometry is kept as clipping.
EffectsDropShadowEffect and BlurEffect.
TextTextBlock, with its Runs and LineBreaks, comes in as Figma text, keeping its font family, size and weight.
PanelsGrid, StackPanel, WrapPanel, DockPanel and Border come in as frames holding their children.
ControlsButton, TextBox, CheckBox, RadioButton, Slider and ProgressBar are drawn with their text, value and checked state.
Resources and stylesBrushes, effects and style setters referenced with {StaticResource} from the same file are applied.

Limitations

LimitationValue
One file, one frameOnly the .xaml you drop is uploaded: a resource dictionary or an image it references from another file isn't part of the import.
Unsupported elementsMediaElement, InkCanvas, WebBrowser, Frame, ItemsControl, ListBox, ComboBox and DataGrid aren't converted as such.
Combined geometryA CombinedGeometry is drawn as a union of its two geometries, whatever its combine mode.
Malformed markupA file that isn't well-formed XML has nothing to convert.
Maximum file size256 MB, on the free tier too. The plugin refuses anything larger on drop.

Privacy & processing

  • The Figma plugin converts your file on the ‹div›RIOTS API. The file is stored only for the processing, then deleted, and never used for training.
  • Anonymous usage analytics are captured (on api.divriots.com) to improve the experience.
  • If an import fails, you can choose to send that one file to us for debugging; nothing is uploaded unless you click that button.

Terms and privacy policies for ‹div›RIOTS products are published at divriots.com/legal.

Pricing

OptionFree tierPaid
Figma plugin5 free imports (files up to 256 MB)Unlimited imports, up to 256 MB, on a paid ‹div›RIOTS ONE plan (Pro or Ultra): 1 credit per import

One subscription for every ‹div›RIOTS product — xaml.to.design included — with a shared credit balance you can top up as needed.

Explore plans

How to use

Figma plugin

  1. Open your Figma file and launch xaml.to.design from the plugins menu.
  2. Drag and drop your .xaml file into the plugin, or click Browse to select it.
  3. Wait while it converts: there is no dialog, the import starts right away.
  4. Your drawing lands in Figma as editable layers — edit directly on the canvas.

FAQ

What file types does xaml.to.design support?

XAML files (.xaml): a drawing on a Canvas, or a screen built from panels and controls, as WPF and other XAML frameworks write them.

Is the result editable, or a flattened image?

Editable. Shapes come in as vectors, text as Figma text, panels as frames, all native Figma layers.

Does it need Visual Studio, Blend or Windows?

No. The plugin sends the file to the ‹div›RIOTS API, which reads the markup itself and rebuilds it as Figma layers. Nothing to install beyond the plugin.

Is there an import dialog?

No. A XAML file is one drawing, so there is nothing to choose: drop the file and it is imported straight away, as editable layers.

What happens to text and fonts?

A TextBlock comes in as Figma text, with its runs and line breaks, keeping its font family, size and weight.

What about resources and styles?

Brushes, effects and styles the file declares as resources and uses through {StaticResource} are applied. Resources in another file (a separate resource dictionary) are not: only the .xaml you drop is uploaded.

Can I use xaml.to.design without Figma?

No. xaml.to.design is a Figma plugin: it runs inside Figma and places the result on your canvas. There is no web tool or API for XAML.

Is xaml.to.design free?

The plugin includes 5 free imports, of files up to 256 MB. Paid ‹div›RIOTS ONE plans (Pro or Ultra) import without a limit, files up to 256 MB, at 1 credit per import.

Support

Need a hand, hit a bug, or have a file that doesn’t import the way you expect? Email us at [email protected], or ask on Discord. Attaching the file (or a screenshot of the result) helps us help you faster.

See also