EMF+ burndown chart
- Input
- 233,976-byte EMF+ chart, 316 × 161 mm.
- Output
- 89,367-byte SVG in under 0.1 s after the layout step.
EMF → SVG takes a Windows-only vector picture to the vector format browsers understand, so an Office chart can go on a web page without turning into pixels.
From real runs
| Element | Result | What happens |
|---|---|---|
| Vector paths | Kept | Bars, gridlines and curves are SVG paths; the burndown chart SVG stays sharp at any browser zoom. |
| Text | Changed | Labels are turned into outlines, so the SVG looks the same without fonts but its text cannot be selected or translated. |
| Embedded bitmaps | Kept | Clip-art that Office built from bitmaps stays bitmap: the server icon's 12 image pieces are embedded inside the 31,615-byte SVG. |
| Picture bounds | Kept | The SVG's view box is trimmed to the drawing, so it drops into an img tag without extra white space. |
| Background | Changed | A white rectangle sits behind the drawing; delete it in an editor if you need the picture on a coloured page. |
| Size of wide pictures | Changed | Pictures wider than A4 are fitted first: the 316 mm burndown chart has a 442 × 249 view box, which only matters if a tool reads the SVG's physical size. |
Bars, gridlines and curves are SVG paths; the burndown chart SVG stays sharp at any browser zoom.
Labels are turned into outlines, so the SVG looks the same without fonts but its text cannot be selected or translated.
Clip-art that Office built from bitmaps stays bitmap: the server icon's 12 image pieces are embedded inside the 31,615-byte SVG.
The SVG's view box is trimmed to the drawing, so it drops into an img tag without extra white space.
A white rectangle sits behind the drawing; delete it in an editor if you need the picture on a coloured page.
Pictures wider than A4 are fitted first: the 316 mm burndown chart has a 442 × 249 view box, which only matters if a tool reads the SVG's physical size.
We converted our Enhanced Metafile (EMF) sample (45 KB) with Office engine → Image engine on 2026-10-20. It took 1.4 s and produced a 31 KB SVG file, 31% smaller than the input. The engine raised 1 warning, listed below.
Input · sample.emf · 45 KB
45,876 bytes
Output · sample.svg · 31 KB
SVG viewBox 0 0 88.22101 92.31561, 51 paths
First lines of the output
<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape" version="1.1" width="88.22101" height="92.31561" viewBox="0 0 88.22101 92.31561">
<defs>
<clipPath id="clip_1">
<path transform="matrix(1,0,0,-1,-253.754,467.20826)" d="M0 .028H595.247V841.88906H0Z" clip-rule="evenodd"/>
</clipPath>
<clipPath id="clip_2">
<path transform="matrix(1,0,0,-1,-253.754,467.20826)" d="M257.3 378.907H337.917V463.039H257.3Z" clip-rule="evenodd"/>
</clipPath>
<clipPath id="clip_3">
<path transform="matrix(1,0,0,-1,-253.754,467.20826)" d="M278.277 383.017V432.028L310.478 450.935V402.519L278.277 383.017Z" clip-rule="evenodd"/>
<…Inkscape
inkscape figure.emf --export-type=svg --export-filename=figure.svgKeeps text as text, but skips many EMF+ records, so Office charts saved with EMF+ only can lose their content.
The HTTP API and the MCP server run the exact engine this page uses (Office engine → Image engine); the response carries the same warnings the web converter shows. Check support first with GET /api/v1/pairs?from=emf&to=svg.
curl -X POST https://filetypeconverters.com/api/v1/convert \
-H "Authorization: Bearer $FTC_API_KEY" \
-F "file=@input.emf" -F "from=emf" -F "to=svg" \
-F 'options={"width":0}' \
--output output.svg| Key | Applies to | Type | Default |
|---|---|---|---|
| width | Writing SVG | number | 0 |
| height | Writing SVG | number | 0 |
| fit | Writing SVG | contain · cover · fill | contain |
| quality | Writing SVG | number | 90 |
| background | Writing SVG | string | #ffffff |
| stripMetadata | Writing SVG | boolean | true |
Yes. It uses plain paths and embedded images with no scripts or external fonts.
It is converted to outlines so it looks right on every machine without installing the original fonts. Edit labels in the source document and export again.
Google Slides imports SVG poorly; use EMF → PNG at a large width for Slides, and keep the SVG for web pages.