
A Figma SVG can look correct while its caption has become shapes. Figma outlines SVG text by default. Turn off Outline text in the SVG export settings when the recipient needs text objects. Keep the Figma source and test a real wording change in the actual receiving editor; an export option alone does not guarantee that editor's text support.
Key Takeaways
- A visually faithful outline and an editable caption are different deliverables.
- Text that cannot be selected and text rendered in the wrong font need different investigations.
- Preserve the source, approved wording and font details for a recoverable handoff.
Define the edit before exporting
Ask whether the next person needs to change a product name, translate a label or simply place approved artwork. An outlined badge can suit placement while blocking the translator's task.
For a hypothetical product card, record the exact change from “Spring Sample” to “Summer Sample.” Moving individual letter shapes does not satisfy a request to edit the phrase as text. This distinction also matters when handing over editable presentation text.
Keep an approved visual rendition for comparison and identify which file is the editable candidate. Do not overwrite the only approved artwork while diagnosing compatibility.
Choose the SVG setting deliberately
Figma's official static-export documentation describes glyph-based SVG text by default and directs users to disable Outline text for editing.
Select the intended export object, choose SVG and inspect the option in its format settings. Export a new candidate. Retain an outlined rendition separately if the receiver also needs a stable placement asset.
Do not infer that another format or a successful text-copy operation provides the same editing structure. The required test is the agreed caption revision in the receiving application.
Separate two receiving-editor failures
If the caption cannot be selected as text, first verify that the new export used Outline text disabled. Then check whether the recipient's application supports editable SVG text through its import route. Shapes in an older export will not regain text structure merely because a newer export setting changed.
If text is selectable but letters change shape or characters disappear, inspect font availability and character coverage. Check accents, punctuation, spacing and line wrapping. The font-and-glyph handoff guide helps distinguish this from an outline issue. Retain accurate font names and licensing information without distributing font software beyond its license.
For the sample card, the replacement wording with a different width may need a layout adjustment even when the font is correct. Inspect the label boundaries and nearby photograph after changing it.
Use a clear recovery route
When the receiving editor cannot support the required SVG text, return the wording change to the retained Figma source and re-export an approved rendition. If the recipient must perform future edits themselves, agree on a format their application supports or deliberately rebuild the caption as text in that tool. Keep the exact wording and approved layout for comparison; do not promise automatic recovery of outlined letters.
Acceptance means the receiver can change the whole phrase, save, reopen and output it with the intended wording and composition. Rotating individual letters is a different operation.
This is documentation-based handoff guidance, not an installed-editor test. Record which receiving application and import route actually passed the agreed edit before calling the file editable.
Related tasks
- How Do I Rotate One Letter in Inkscape Without Converting the Word to Paths?
- Why Does My Print PDF Show the Wrong Font or Empty Character Boxes?
- How Do I Put AI Artwork into PowerPoint While Keeping the Slide Text Editable?
Sources and scope
- Export formats and settings for static designs: Documented SVG text-outline setting; font and receiving-editor recovery checks are proposed handoff procedures.
Documentation-based guidance. The caption example and receiving-editor checks are proposed, not measured software tests.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.