离线 · 无上传 · 浏览器本地完成Offline · no uploads · runs in the browser

SVG 转 Word——离线、矢量在第二步变位图、结果会写明SVG to Word offline — the vector turns bitmap in step two

这条最容易被讲反的地方是「**在哪一步变成位图**」。`svg>html` 那一步**不栅格化**——它把图形作为矢量留在页面里（净化用的是保留 svg 与 svgFilters 的配置，脚本与事件属性去掉，渐变滤镜这些可见结果留下）。真正变位图的是第二步 `html>docx`：它在净化**之前**把文档里每一个内联 SVG 逐个取出来，走「剥活动性内容 → 规范化尺寸 → 画进画布 → 输出 PNG 数据 URL」，再把 `<img>` 换上去。顺序是有原因的：净化用的 html profile 里**根本没有 svg 标签**，如果先净化，用户的图会被当成可执行标记一起删掉，产物是一份合法但空白的 .docx，而界面还报成功。栅格化时按最长边钳制到本扩展的图片上限、**只缩不放**，所以巨大的 SVG 不会撑爆画布，小的也不会被硬拉大。之后 `html>docx` 才净化、剥掉远程引用并交给打包器——那份 PNG 数据 URL 会被提成包里独立的图片部件，`Word` 显示它不需要取数。两件对用户可见的事：结果卡会写明**这一次发生过栅格化**（界面上单独一行提示，不是只写在文档里），以及产物是 altChunk 包装——排版与分页由打开它的程序决定。代价要说清：**缩放不再无损**，进 Word 之后它是一张位图，放大就是像素；想要保留矢量就不要进 Word（SVG→HTML 保留矢量，SVG→PDF 那一条第一步就 `svg>png` 栅格化，反而不是留矢量的路）。依赖 `<use>` 的雪碧图这一类要特别注意：`<symbol>` 的定义会被 svg profile 留下、引用层去掉，栅格化出来的往往是空图——那种文件更适合先 SVG→PNG 再交给 Word。全程只有 storage 权限，不联网。The thing most often stated backwards about this route is **which step turns it into a bitmap**. `svg>html` does not rasterise — the artwork stays vector in the page, sanitised with a profile that keeps `svg` and `svgFilters`, so scripts and event handlers go while gradients and filters survive. The bitmap happens in step two, `html>docx`: **before** sanitising, it takes each inline SVG out of the document and runs it through «strip active content → normalise the size → draw on a canvas → emit a PNG data URL», swapping in an `<img>` afterwards. The order is load-bearing: the html profile this step sanitises with has **no svg tags at all**, so sanitising first would delete the user’s diagram as if it were executable markup and hand back a valid, blank .docx that the interface reported as a success. Rasterisation clamps the longest edge to this extension’s image ceiling and **only ever scales down**, so an enormous SVG cannot blow up the canvas and a small one is not stretched. Only then does `html>docx` sanitise, strip remote references and hand the markup to the packer — that PNG data URL becomes its own image part inside the package, so nothing has to be fetched to display it. Two things are visible to the user: the result card **says when rasterisation happened** (a line of its own in the interface, not just fine print on this page), and the artifact is an altChunk wrapper, so layout and paging belong to whichever program opens it. Say the cost plainly: **zooming is no longer lossless** — inside Word it is a bitmap, and enlarging shows pixels. If keeping the vector matters, do not go into Word (SVG to HTML keeps it vector; SVG to PDF rasterises in its very first step, so it is not the vector-preserving road either). One input shape deserves its own warning: a sprite built on `<use>` keeps its `<symbol>` definitions but loses the referencing layer, so what rasterises is often an empty picture — those files are better taken SVG to PNG first, then into Word. All of it on the storage permission, with no network at all.