Generator or Producer Name Included in Output Documents

You can easily know if a document is produced by using Aspose.Words for Node.js via .NET. You can also find the version number of Aspose.Words for Node.js via .NET that was used to create a particular output document. Aspose.Words directly writes this information into the generated document.

The version number is specified in the format YY.MM.N or YY.M.N, for example, 24.12.0 or 25.4.0.
Here YY is the last two digits of the release year, M or MM is the release month (1–12), and N is the minor release number. Usually, N is “0”.

Note that you can instruct Aspose.Words to remove this information from output documents.

Depending on the output file format, the following table lists the ways that you can use to know the generator name and version number.

SaveFormat Value	String, Comment, or Field Written in the File	How to Find
`Doc`	`AWN.YY.M.N` For example, `AWN.24.12.0`	DOC generated by Aspose.Words gets 8 bytes written. You can check it by opening the file in some binary editor.
`Dot`	`AWN.YY.M.N` For example, `AWN.24.12.0`	DOT generated by Aspose.Words gets 8 bytes written. You can check it by opening the file in some binary editor.
`Docx`	`<!-- Generated by Aspose.Words for Node.js via .NET YY.M.N -->` For example, `<!-- Generated by Aspose.Words for Node.js via .NET 24.12.0 -->`	Rename the file as .zip. Extract the ZIP. Open ~/Word/Document.xml to see this comment.
`Docm`	`<!-- Generated by Aspose.Words for Node.js via .NET YY.M.N -->` For example, `<!-- Generated by Aspose.Words for Node.js via .NET 24.12.0 -->`	Rename the file as .zip. Extract the ZIP. Open ~/Word/Document.xml to see this comment.
`Dotx`	`<!-- Generated by Aspose.Words for Node.js via .NET YY.M.N -->` For example, `<!-- Generated by Aspose.Words for Node.js via .NET 24.12.0 -->`	Rename the file as .zip. Extract the ZIP. Open ~/Document.xml to see this comment.
`Dotm`	`<!-- Generated by Aspose.Words for Node.js via .NET YY.M.N -->` For example, `<!-- Generated by Aspose.Words for Node.js via .NET 24.12.0 -->`	Rename the file as .zip. Extract the ZIP. Open ~/Word/Document.xml to see this comment.
`FlatOpc`	`<!-- Generated by Aspose.Words for Node.js via .NET YY.M.N -->` For example, `<!-- Generated by Aspose.Words for Node.js via .NET 24.12.0 -->`	.xml file contains this comment. You can open it in Notepad to see this comment.
`FlatOpcMacroEnabled`	`<!-- Generated by Aspose.Words for Node.js via .NET YY.M.N -->` For example, `<!-- Generated by Aspose.Words for Node.js via .NET 24.12.0 -->`	.xml file contains this comment. You can open it in Notepad to see this comment.
`FlatOpcTemplate`	`<!-- Generated by Aspose.Words for Node.js via .NET YY.M.N -->` For example, `<!-- Generated by Aspose.Words for Node.js via .NET 24.12.0 -->`	.xml file contains this comment. You can open it in Notepad to see this comment.
`FlatOpcTemplateMacroEnabled`	`<!-- Generated by Aspose.Words for Node.js via .NET YY.M.N -->` For example, `<!-- Generated by Aspose.Words for Node.js via .NET 24.12.0 -->`	.xml file contains this comment. You can open it in Notepad to see this comment.
`Rtf`	`{\\generator Aspose.Words for Node.js via .NET YY.M.N;}` For example, `{\\generator Aspose.Words for Node.js via .NET 24.12.0;}`	.rtf file contains this comment. You can open it in Notepad to see this comment.
`WordML`	`<!-- Generated by Aspose.Words for Node.js via .NET YY.M.N -->` For example, `<!-- Generated by Aspose.Words for Node.js via .NET 24.12.0 -->`	.xml file contains this comment. You can open it in Notepad to see this comment.
Pdf	Application: Aspose.Words PDF Producer: `Aspose.Words for Node.js via .NET YY.M.N`, for example, `Aspose.Words for Node.js via .NET 24.12.0`
`Xps`	`<!-- Generated by Aspose.Words for Node.js via .NET YY.M.N -->` For example, `<!-- Generated by Aspose.Words for Node.js via .NET 24.12.0 -->`	Rename the file as .zip. Extract the ZIP. In XPS this comment can be found in ~/Documents/1/Pages/1.fpage
`XamlFixed`	`<!-- Generated by Aspose.Words for Node.js via .NET YY.M.N -->` For example, `<!-- Generated by Aspose.Words for Node.js via .NET 24.12.0 -->`	.xml file contains this comment. You can open it in Notepad to see this comment.
`Svg`	`<!-- Generated by Aspose.Words for Node.js via .NET YY.M.N -->` For example, `<!-- Generated by Aspose.Words for Node.js via .NET 24.12.0 -->`	.xml file contains this comment. You can open it in Notepad to see this comment.
`HtmlFixed`	`<meta name="generator" content="Aspose.Words for Node.js via .NET YY.M.N" />` For example, `<meta name="generator" content="Aspose.Words for Node.js via .NET 24.12.0" />`	HTML file contains this tag. You can open it in Notepad to see.
`OpenXps`	`<!-- Generated by Aspose.Words for Node.js via .NET YY.M.N -->` For example, `<!-- Generated by Aspose.Words for Node.js via .NET 24.12.0 -->`	Rename the file as .zip. Extract the ZIP. In OpenXps this comment can be found in ~/Documents/1/Pages/1.fpage
`Ps`	`%Generated by Aspose.Words for Node.js via .NET YY.M.N` For example, `%Generated by Aspose.Words for Node.js via .NET 24.12.0`	.ps file contains this comment. You can open it in Notepad to see this comment.
`Pcl`	–	–
`Html`	`<meta name="generator" content="Aspose.Words for Node.js via .NET YY.M.N" />` For example, `<meta name="generator" content="Aspose.Words for Node.js via .NET 24.12.0" />`	HTML file contains this tag. You can open it in Notepad to see.
`Mhtml`	`<meta name="generator" content="Aspose.Words for Node.js via .NET YY.M.N" />` For example, `<meta name="generator" content="Aspose.Words for Node.js via .NET 24.12.0" />`	MHTML file contains this tag. You can open it in Notepad to see.
`Epub`	`<meta name="generator" content="Aspose.Words for Node.js via .NET YY.M.N" />` For example, `<meta name="generator" content="Aspose.Words for Node.js via .NET 24.12.0" />`	Rename the file as .zip. Extract the ZIP. Go to ~/OEBPS/<file_name>.html.
`Odt`	`<!-- Generated by Aspose.Words for Node.js via .NET YY.M.N -->` For example, `<!-- Generated by Aspose.Words for Node.js via .NET 24.12.0 -->`	Rename the file as .zip. Extract the ZIP. Check it in ~/content.xml
`Ott`	`<!-- Generated by Aspose.Words for Node.js via .NET YY.M.N -->` For example, `<!-- Generated by Aspose.Words for Node.js via .NET 24.12.0 -->`	Rename the file as .zip. Extract the ZIP. Check it in ~/content.xml
`Text`	–	–
`XamlFlow`	`<!-- Generated by Aspose.Words for Node.js via .NET YY.M.N -->` For example, `<!-- Generated by Aspose.Words for Node.js via .NET 24.12.0 -->`	.xml file contains this comment. You can open it in Notepad to see this comment.
`XamlFlowPack`	`<!-- Generated by Aspose.Words for Node.js via .NET YY.M.N -->` For example, `<!-- Generated by Aspose.Words for Node.js via .NET 24.12.0 -->`	.xml file contains this comment. You can open it in Notepad to see this comment.
`Markdown`	–	–
`Tiff`	–	–
`Png`	–	–
`Bmp`	–	–
`Emf`	–	–
`Jpeg`	–	–
`Gif`	–	–

Also there is an addition to the variants shown in the table. The version number of Aspose.Words can be written in several more places for some formats. It depends on the export settings.

These additional situations are not described in the table above.

FAQ

Q: How can I find the generator name and version that Aspose.Words added to a saved document?
A: The generator information is stored differently depending on the output format. For binary formats like DOC and DOT it appears as an 8‑byte string (AWN.YY.M.N). For XML‑based formats (DOCX, DOCM, HTML, etc.) it is written as a comment or a <meta name="generator"> tag. Open the file with a binary editor, unzip the package, or view the source to locate the string as described in the table.
Q: I want to prevent Aspose.Words from writing the generator name and version into my output files. How do I do that?
A: Set the RemoveGeneratorInfo property on the appropriate SaveOptions object before calling Document.Save. Example for PDF:
```
Aspose.Words.Document doc = new Aspose.Words.Document("input.docx");
Aspose.Words.Saving.PdfSaveOptions saveOptions = new Aspose.Words.Saving.PdfSaveOptions();
saveOptions.RemoveGeneratorInfo = true;
doc.Save("output.pdf", saveOptions);
```
The same property exists on other format‑specific SaveOptions classes (e.g., DocxSaveOptions, HtmlSaveOptions).
Q: Which SaveOptions class should I use to control the generator information for a specific format?
A: Use the format‑specific SaveOptions class that matches the desired output. For example:
- DOCX: Aspose.Words.Saving.DocxSaveOptions
- HTML: Aspose.Words.Saving.HtmlSaveOptions
- PDF: Aspose.Words.Saving.PdfSaveOptions
  After creating the appropriate options object, set RemoveGeneratorInfo = true and pass it to Document.Save.
Q: Does the presence of a license affect the generator information?
A: No. The generator string is written regardless of licensing. However, a valid license removes the evaluation watermark; the generator info can still be removed independently using RemoveGeneratorInfo.

Structured Document Tags