# Aspose.Words Documentation
Central documentation hub for Aspose.Words across all supported platforms.
Easily create, edit, render, print your documents, as well as convert them to almost any format, such as DOC, DOCX, RTF, HTML, Markdown, PDF, XPS, EPUB, and more. All this without additional libraries and applications.
## Platforms
- [.NET Documentation](https://docs.aspose.com/words/net/): Documentation and useful links for the Aspose.Words library for .NET developers
- [Java Documentation](https://docs.aspose.com/words/java/): Guides and useful links for the Aspose.Words library for Java developers
- [C++ Documentation](https://docs.aspose.com/words/cpp/): Documentation and useful links for the Aspose.Words library for C++ developers
- [Python Documentation](https://docs.aspose.com/words/python-net/): Documentation and useful links for the Aspose.Words library for Python developers
- [Node.js Documentation](https://docs.aspose.com/words/nodejs-net/): Documentation and useful links for the Aspose.Words library for Node.js developers
- [Android via Java](https://docs.aspose.com/words/java/android/): Using Aspose.Words on Android
## Additional Resources
- [Release Notes](https://releases.aspose.com/words/): Product updates and version history
- [Product Overview](https://products.aspose.com/words/): Features and supported formats
- [API Reference Hub](https://reference.aspose.com/words/): Links to all API references
Measured from the saved file
Linked document
UTF-8 text size
1.4 KB1442 bytes
Token count
334o200k_base encoding
Markdown links
99 distinct URLs
Fenced code blocks
016 lines in the file
Size measures the captured UTF-8 text, not compressed transfer size. Tokens are counted with a named tokenizer; other models can count differently. Neither measure establishes context compatibility or answer quality.
Project H1
Aspose.Words Documentation
Context architecture
How the content is divided
2 H2 sections organize 9 parsed Markdown links. 0 links point to .md or .markdown paths; 3 link occurrences use another hostname. Linked destinations have not been recursively validated.
H2 section
Links
UTF-8 bytes
Tokens
PlatformsLine 5
6
814
190
Additional ResourcesLine 13
3
267
63
Link counts exclude parsed fenced and inline code and resolve relative destinations against the final endpoint. Section sizes cover the text below each H2 until the next H2.
Embedded material
Code, installation and API examples
Fenced blocks
0 closed
Declared languages
No fenced blocks detected
Package-install commands
0 detected in fenced or inline code
Authentication examples
0 fenced lines match API-key, Authorization, Bearer, OAuth or access-token patterns
HTTP request examples
0 fenced lines match request-method patterns
Authentication links
0 links have authentication-related labels
Embedded example text and links to further documentation are counted separately. A code block does not establish that a sample runs or that an authentication flow succeeds.
Publisher prioritization
The Optional section
No H2 section named “Optional” was detected in this file.
The community proposal uses Optional by convention for secondary links that can be skipped for a shorter context. This label does not establish that everything outside it is critical, or that the material inside it is deprecated.
Machine-readable routes
MCP references and configuration text
No MCP or Model Context Protocol term was detected in the captured file. 0 links have MCP-related labels or paths. 0 fenced lines match mcpServers, mcp_servers or an mcp add command.
These are text and link observations. No MCP server connection, authentication or tool call was tested.
A verified text response establishes a companion at the checked URL. It does not prove the bundle contains all product documentation, that generation is automated, or that it fits an assistant’s context window.
Change evidence
What can be said about freshness
This capture establishes a baseline. Update frequency cannot be determined from one observation.
Linked release and migration material
1 links have release, changelog, deprecation or migration terms in their labels or paths. These provide places to investigate product changes separately.
File changes can reveal documentation edits or navigation changes. They do not by themselves measure product release velocity, accuracy, agent adoption or AI visibility.
Counts use a deterministic parser, not a spec-compliance grade. Unusual Markdown and indented code can fall outside its recognized patterns. See the llms.txt proposal and tokenizer implementation.