Colleagues discussing documents at an office desk
Illustrative stock photograph. Pexels. Not a product screenshot or evidence of a test.

Dragon Auto-Text Loses Formatting: Check Plain Text and the Destination

Dragon's Plain Text option makes Auto-Text adopt the style of preceding document text. If a saved block arrives without its original font or emphasis, check this option and the destination application's formatting support before recreating the command.

This article concerns Auto-Text in Dragon desktop for Windows. Dragon Professional Anywhere has its own configuration and release behavior; do not assume the same screen or product rules apply. Use generic sample wording because Nuance prohibits using Auto-Text to store private information or credentials.

Decide which formatting behavior you actually want

A reusable paragraph can either blend into the current document or retain a deliberately prepared appearance. Both can be appropriate. Problems arise when the author expects one behavior but the command is configured for the other.

For example, a standard explanatory sentence may need the recipient document's typeface. A nonconfidential report heading may need consistent emphasis. Write down the requirement before changing the command; otherwise a visually different insertion can be mistaken for a fault even when it follows the selected setting.

Inspect a copy of the command

Open the Auto-Text editor through the supported command management interface. Record the current state or create a permitted test command with a distinctive name. Avoid experimenting on a shared production command whose output other staff rely on.

Nuance's Auto-Text editor reference explains the Plain Text choice and its relationship to preserved formatting. It also identifies rich text support as a condition for retaining the formatting supplied in the editor.

Compare the editor with the receiving application

Create a two-sentence sample with one plainly visible formatting difference. Insert it into a blank document in a supported rich text application, then into the actual destination. Keep the command content identical between tests so you can isolate the receiver's behavior.

When the sample blends into the document

If Plain Text is selected, inheriting nearby formatting may be the intended result. Clear the option only when preserved formatting is required and the destination supports it. Saving the command with the required choice is different from manually restyling one previously inserted paragraph.

When only one application loses the style

A destination may accept plain text only, strip incoming formatting or impose a document template. Compare a normal formatted paste into that same field. If that also loses styling, replacing the microphone or repeatedly training the command name will not add rich text capability.

Test resultLikely area to inspect
Formatting missing in every destinationSaved command content and Plain Text setting
Formatting survives in Word onlyDestination formatting capabilities
Text inherits preceding styleWhether Plain Text is intentionally enabled
Command inserts the wrong wordingSelected command and profile, before visual styling
Business workspace with colleagues and office equipment
Illustrative stock photograph of workplace activity, not a product screenshot or a test result. Photo: Pexels.

Keep the command content appropriate

The official Auto-Text overview describes these commands as reusable text or graphics, with optional variable fields. Its privacy restriction matters even for a convenient template: do not embed personal records, health information or credentials in the stored block.

Use neutral prompts for information that must be supplied later through an authorized workflow. A template is not a secure repository merely because its editor sits inside a licensed dictation application.

Verify an insertion from beginning to end

After saving the intended configuration, place the insertion point in a fresh destination paragraph. Run the command, inspect spacing and paragraph breaks, and save and reopen the result. If the block includes a graphic, confirm that the destination actually retains it rather than showing an empty placeholder.

Check the boundary with surrounding text

Look at the first and last characters of the inserted block. A technically preserved font is insufficient if the command merges two paragraphs or leaves unexpected spacing. Test insertion at the location where people will normally use it, not only in an empty document.

For hardware questions unrelated to styling, our PowerMic comparison covers the physical dictation setup. An audio device does not determine whether a target editor supports rich text.

Reusable text needs both the intended appearance and completed placeholders. Review the related guide on Dragon Auto-Text Fields: Remove Delimiters Safely.

Keep a brief note of the command name, profile, target application and desired formatting behavior. This makes the next review repeatable and prevents a colleague from enabling Plain Text to solve one document's appearance while unintentionally changing a template used elsewhere.