Open XML Formats and file name extensions - Office Support Admin Open XML Formats and file name extensions Applies To: Excel 2013 Word 2013 PowerPoint 2013 Excel 2010 Word 2010 PowerPoint 2010 Excel 2007 Word 2007 PowerPoint 2007 Office 2007 Office 2010 More... Less Starting with the 2007 Microsoft Office system, Microsoft Office uses the XML-based file formats, such as .docx, .xlsx, and .pptx. These formats and file name extensions apply to Microsoft Word, Microsoft Excel, and Microsoft PowerPoint. This article discusses key benefits of the format, describes the file name extensions and discusses how you can share Office files with people who are using earlier versions of Office. In this article Can different versions of Office share the same files? What are the benefits of Open XML Formats? The Open XML Formats include many benefits — not only for developers and the solutions that they build, but also for individual people and organizations of all sizes: Compact files Files are automatically compressed and can be up to 75 percent smaller in some cases.

The Open XML Format uses zip compression technology to store documents, offering potential cost savings as it reduces the disk space required to store files and decreases the bandwidth needed to send files via e-mail, over networks, and across the Internet. When you open a file, it is automatically unzipped. When you save a file, it is automatically zipped again. You do not have to install any special zip utilities to open and close files in Office. Improved damaged-file recovery Files are structured in a modular fashion that keeps different data components in the file separate from each other. This allows files to be opened even if a component within the file (for example, a chart or table) is damaged or corrupted. Better privacy and more control over personal information Documents can be shared confidentially, because personally identifiable information and business-sensitive information, such as author names, comments, tracked changes, and file paths can be easily identified and removed by using Document Inspector. Better integration and interoperability of business data Using Open XML Formats as the data interoperability framework for the Office set of products means that documents, worksheets, presentations, and forms can be saved in an XML file format that is freely available for anyone to use and to license, royalty free.

Office also supports customer-defined XML Schemas that enhance the existing Office document types. This means that customers can easily unlock information in existing systems and act upon it in familiar Office programs. Information that is created within Office can be easily used by other business applications. All you need to open and edit an Office file is a ZIP utility and an XML editor. Easier detection of documents that contain macros Files that are saved by using the default "x" suffix (such as .docx, .xlsx, and .pptx) cannot contain Visual Basic for Applications (VBA) macros and XLM macros. Only files whose file name extension ends with an "m" (such as .docm, .xlsm, and .pptm) can contain macros. Top of Page What are the XML file name extensions? By default, documents, worksheets, and presentations that you create in Office are saved in XML format with file name extensions that add an "x" or an "m" to the file name extensions that you are already familiar with. The "x" signifies an XML file that has no macros, and the "m" signifies an XML file that does contain macros.

For example, when you save a document in Word, the file now uses the .docx file name extension by default, instead of the .doc file name extension. When you save a file as a template, you see the same kind of change. The template extension used in earlier versions is there, but it now has an "x" or an "m" on the end. If the file contains code or macros, you must save it by using the new macro-enabled XML file format, which adds an "m" for macro to the file extension. The following tables list all the default file name extensions in Word, Excel, and PowerPoint. Word Top of Page Can different versions of Office share the same files? Office lets you save files in the Open XML Formats and in the binary file format of earlier versions of Office and includes compatibility checkers and file converters to allow file-sharing between different versions of Office. Opening existing files in Office You can open and work on a file that was created in an earlier version of Office, and then save it in its existing format.

Because you might be working on a document with someone who uses an earlier version of Office, Office uses a compatibility checker that verifies that you have not introduced a feature that an earlier version of Office does not support. When you save the file, the compatibility checker reports those features to you and then lets you remove them before continuing with the save. Opening Office files in earlier versions of Office You can open and change an Office file in Microsoft Word, Excel, or PowerPoint 2003 by downloading the necessary file converters. On the computer that uses an earlier version of Office, go to the Download Center and download the Microsoft Office Compatibility Pack for 2007 Office Word, Excel and PowerPoint File Formats. Important: For the converters to work, the earlier version of Microsoft Office must first be updated to one of the service packs listed here. After you have installed the service pack for your version of Office, download the converter.

How to use components of the .NET Framework 3.0 to create and then to stream an Office Word 2007 document and an Office Excel 2007 workbook to a client computer  Find downloads CV: LZqTnntBWj19nc20.0 How to use components of the .NET Framework 3.0 to create and then to stream an Office Word 2007 document and an Office Excel 2007 workbook to a client computer Select Product Version INTRODUCTION This article describes how to use components of the Microsoft .NET Framework 3.0 to perform the following actions: Note You do not have to install the Microsoft 2007 Office System or its components on the server to follow the steps that are described in the "More Information" section. However, you must have the .NET Framework 3.0 installed on the server. By default, the .NET Framework 3.0 is included with Windows Vista. However, if the server is running a different version of Windows, you may have to download and then install the .NET Framework 3.0.

To obtain the .NET Framework 3.0, visit the following Microsoft Web site: Additionally, you can use the 2007 Office system on the client computer to follow the steps that are described in the "More Information" section. However, you can also use an earlier version of the Office system. If the client computer has Microsoft Office 2003, Microsoft Office XP, or Microsoft Office 2000 installed, you must install the free Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats to follow the steps that are described in the "More Information" section. To obtain the Office Compatibility Pack, visit the following Microsoft Web site: The steps that are described in the "More Information" section use the files in the StreamingOfficeSample.exe sample package. You can download the StreamingOfficeSample.exe sample package from Microsoft. The following file is available for download from the Microsoft Download Center: For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base: 119591 How to obtain Microsoft support files from online services Microsoft scanned this file for viruses.

Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file. More Information The StreamingOfficeSample.exe sample package contains the following: A Web form The DocumentGenerator class library project The WorkBookGenerator class library project The Web form and the class library projects were created by using Microsoft Visual C# 2005. The Web form The Web form connects to the Northwind sample database that is included with Microsoft Office Access 2003. Note You do not have to have Office Access 2003 installed to use the sample package. The Web form uses data from the following tables to display an online order lookup form: Customers Order Details Products You can use the Web form to select a customer in a list. After you select the customer, the Web form filters the list of orders. The filtered list shows only orders for the selected customer. When you select an order in the list, the details for the order appear in the data grid control on the Web form.

Then, you can click the buttons on the Web form to perform the following actions: Create a report that is based on the selected data The code creates this report as a Word 2007 document and then streams the document to the client computer. Export the order details data to a new Excel workbook The code creates an Excel 2007 workbook and then streams the workbook to the client computer. The DocumentGenerator class library project The code in the DocumentGenerator class library project uses the Packaging components in the WindowsBase.dll assembly to create the Word document. The WindowsBase.dll assembly is included with the .NET Framework 3.0. This class library project contains the NwindTemplate.docx file as an embedded resource. The Packaging components in the WindowsBase.dll assembly read the contents of the NwindTemplate.docx file into a package object. The Packaging components use the methods in the clsCreateDocument class to perform the following actions: Create a Word 2007 document in the temporary folder on the server This Word document is based on the NWindTemplate.docx file.

Add various parts and various data to the Word document from the Web form When the Word document is complete, the code in the DocumentGenerator class library project streams the Word document to the client computer. The WorkBookGenerator class library project The code in the WorkBookGenerator class library project uses the Packaging components in the WindowsBase.dll assembly to perform the following actions: Export the order details data to a new Excel workbook To do this, the Packaging components read the data into an Array list object. Create an Excel workbook in the temporary folder on the server The Packaging components, together with the methods in the clsCreateWorkbook class, add the workbook parts and the data to the Excel workbook from the Web form. When the Excel workbook is complete, the code in the WorkBookGenerator class library project streams the workbook to the client computer. Test the sample To test the sample, you will perform the following actions: Add the sample project to the Web server On a client computer, visit the sample project Web site that you created Download the Word document report and the Excel workbook To do this, follow these steps. Add the sample project to the Web server Download the sample package file.

Create the following folder on the Web server: C:\Inetpub\wwwroot\StreamingOffice2007Sample Extract the contents of the sample package file to the folder that you created in step 2. Use IIS Manager to create a virtual directory. To do this, follow these steps: Click Start, click Run, type inetmgr, and then click OK. Expand the server name, and then expand Web Sites. Right-click Default Web Site, point to New, and then click Virtual Directory. The Virtual Directory Creation Wizard starts. In the Virtual Directory Creation Wizard, click Next. In the Alias box, type an alias for the virtual directory. For example, type StreamingOffice2007Sample. Click Next. Click Browse, locate the folder that you created in step 2, and then click Next. Click to select the Read check box and the Run scripts (such as ASP) check box. Make sure that the other check boxes are cleared, and then click Next. Click Finish to complete the wizard. For ASP content, you may want to confirm that an application was created. To do this, follow these steps: Right-click the virtual directory that you created in the previous steps, and then click Properties.

On the Virtual Directory tab, make sure that the virtual directory alias is listed in the Application name box under Application Settings. If the virtual directory alias is not listed, click Create. Note The application name does not have to match the virtual directory alias that you typed in step 4e of the previous steps. Click the ASP.NET tab. Verify that ASP.NET version is set to 2.0.50727. If it is not, select 2.0.50727 in the ASP.NET versionlist, and then click Apply.

Visit the sample project Web site, and then download the Word document report and the Excel workbook Note The client computer that you will use for the following steps must have one of the following installed: Microsoft Office Word 2007 and Microsoft Office Excel 2007 Microsoft Office Compatibility Pack for Word, Excel, and PowerPoint 2007 File Formats On a client computer, follow these steps: Start a Web browser such as Microsoft Internet Explorer, and then visit the following Web site: Introducing the Office (2007) Open XML File Formats Introducing the Office (2007) Open XML File Formats Collapse the table of content Expand the table of content This documentation is archived and is not being maintained. This documentation is archived and is not being maintained. This documentation is archived and is not being maintained. Introducing the Office (2007) Open XML File Formats Office 2007 Summary: Learn the benefits of the Office Open XML Formats. Users can exchange data between Office applications and enterprise systems using XML and ZIP technologies. Documents are universally accessible. And, you reduce the risk of damaged files.

(26 printed pages) Frank Rice, Microsoft Corporation May 2006 Applies to: 2007 Microsoft Office Suites, Microsoft Office Excel 2007, Microsoft Office PowerPoint 2007, Microsoft Office Word 2007 Contents Introduction to the Office Open XML File Formats Following the advent of XML in the 1990s, corporate computing customers began to realize the business value in adopting open formats and standardization in the computer products and applications that they relied on. IT professionals benefited from the common data format possible with XML because of its capacity to be read by applications, platforms, and Internet browsers. Likewise, with the adoption of support for XML in Microsoft Office 2000, developers began to see the need to transition from the binary file formats seen in previous versions of Microsoft Office to the XML format. Binary files (.doc, .dot, .xls, and .ppt files), which for years did a great job of storing and transporting data, were not able to meet the new workplace challenges that included easily moving data between disparate applications, and allowing users to glean business insight from that data.

The 2007 Microsoft Office system continues with this transition by adopting an XML-based file format for Microsoft Office Excel 2007, Microsoft Office Word 2007, and Microsoft Office PowerPoint 2007. The new file format, called Office Open XML Formats, addresses these workplace issues with changes that affect the way that you approach solutions based on Microsoft Office documents. The new formats improve file and data management, data recovery, and interoperability with line-of-business systems. They extend what is possible with the binary files of earlier versions. Any application that supports XML can access and work with data in the new file format. The application does not need to be part of the Microsoft Office system or even a Microsoft product. Users can also use standard transformations to extract or repurpose the data. In addition, security concerns are drastically reduced because the information is stored in XML, which is essentially plain text. Thus, the data can pass through corporate firewalls without hindrance. Note Do not confuse the Office XML Formats with the Microsoft Windows XML Paper Specification format. Office XML Formats use the Open Packaging Conventions, also used by the XML Paper Specification (XPS). However, the formats are different in several important ways.

The XPS is a paginated, fixed document format introduced for the Microsoft Windows Vista operating system. Office XML Formats are fully editable file formats for Office Word 2007, Office Excel 2007, and Office PowerPoint 2007. Although they share similarities in their use of XML and ZIP compression, they are different in file format design and intended use. For more information, see the Open XML Formats Resource Center . New File Format Scenarios The Office XML Formats change the way that customers work with data. Consider some of the following scenarios, now possible with the new file formats: A server-side process can read one of the items out of a ZIP archive without having to extract them all. For example, you can extract only the XML file containing the document's data without opening the files that contain the document's formatting, properties, and other peripheral information. In most scenarios, the new file container is transparent to the user. It looks like a typical binary document file. However, the new XML format document is compressed and smaller, making it easier to send to other users through e-mail or on other media.

Virus scanners and server applications can easily extract the container to view just the items affected directly, without the worry of corrupting the container or the contents inside. Files that are saved in the new file format cannot contain executable macro code. (This does not apply to macro-enabled files, discussed elsewhere in this article.) Therefore, they are considered "safe" and can pass through firewalls and be sent through e-mail applications without security concerns. This behavior is enforced by the Microsoft Office applications. If a macro part is added to an Office XML Format document, Office prevents opening the document. Note Some ZIP applications allow you to create encrypted files. The new file format does not create encrypted files. If you attempt to read an encrypted file, it stops reading the file and returns an error. If one item in the container becomes corrupted, the other items continue to be available. For example, if a user tries to open a file created from a damaged disk and the file is corrupt, the Office file-recovery mechanism rebuilds the central directory and fully recovers the contents of the file. Office developers can use Microsoft WinFX application programming interfaces (APIs) to create a valid XPS file. These APIs are the way that solutions interact with the content of the new file format.

Office developers can also use the APIs to open a ZIP archive created by another ZIP application, assuming it does not use one of the ZIP features not supported by Office. Note Microsoft Office creates files conforming to the Open Packaging Conventions that the WinFX APIs can read, and conversely, WinFX can create packages that you can open using Microsoft Office applications. The WinFX APIs work with previous versions of Microsoft Windows, including the following: Microsoft Windows Vista, Microsoft Windows Server 2003, and Microsoft Windows XP. Additionally, converters are available for Microsoft Office 2000, Microsoft Office XP, and Microsoft Office 2003 Editions. The new file format also changes the way that Office users work with the applications that they use in their daily tasks. The following scenarios illustrate ways that the new format changes the way that you accomplish work using the 2007 Office release: Howard, a curious user, finds that the new file format container in the 2007 Office release is a ZIP file. Howard wants to see this for himself, so he opens one of the documents he created in Word 2007 using a ZIP application.

He sees some files that look like XML document content, and a few images that match what he had seen in the original document. Intrigued, the curious Howard opens one of the XML files in Notepad to see what sort of XML file Word generates. Satisfied at how easy it is to peer inside the document, he closes Notepad and the ZIP application and reopens the file in Word to continue working on the document. Jan needs to change a document property in her Word 2007 document. She opens the new format file in a ZIP product, extracts the XML item containing the document properties, makes the change, adds the item back into the container, and then saves and closes the container. She then opens the document in Word, and finds that all of her content is still there and that the only change is to the property that she modified. The logo for a consulting company changed to reflect its new mission. The IT department is given the task of changing the logo in the thousands of documents currently stored on a server. In previous versions of Microsoft Office, it was necessary to either open each document individually and delete the old logo and paste the new logo, or to create and test a complex custom application to automate the task.

With the new file format, the IT department creates a batch process that navigates the file structure to locate the graphic in the media folder (which is the same for each document) and swaps out the new graphic. Now when the document opens, the new logo automatically displays. A law firm must protect the confidentiality of their customer's data and of their own data. Based on standard practices, the firm knows that documents, including those created in Word, store several properties—some visible and some hidden within the document. Some of those properties can contain information that is customer-sensitive and company proprietary. Through trial and error, the firm created a procedure to remove this information. However, the process is time-consuming and, because it is dependent on the user following the procedure exactly, subject to mistakes. With the new file format, the IT department develops a simple batch process that walks the folder structure to remove the targeted parts in the package. The firm can now be confident that all sensitive and propriety information is safely removed from the document. Denise is putting the final changes on the dissertation for her master's degree. After adding the bibliography, she prepares to perform the final save.

Much to her horror, the save stops prematurely and she sees a message telling her that the document appears to be corrupt. After the shock subsides, Denise remembers that she is using the new file format. She imports the text into a new document, reattaches the pictures, and includes the formatting and style parts to reconstruct the document successfully. She then saves the new document. Elizabeth is a Windows 2000 user who runs Office 2000 with the converter installed that is included in the 2007 Office release. She can open a Word XML Format document. In addition, she can edit the document and re-save it as a document in the new format because the converters provide open and save support. The new Office XML Formats introduce a number of benefits that help not only developers and the solutions they build, but also individual users and organizations of all sizes. The following highlights are some of the additional overall benefits of the Office XML Formats: Easily integrate business information with documents. Office XML Formats enable rapid creation of documents from disparate data sources, accelerating document assembly, data mining, and content reuse. Exchanging data between Office applications and enterprise business systems is simplified.

In addition, you can alter the information inside an Office document or create one from the document's components without using the Office application. Employees can improve productivity by publishing, searching, and reusing information more quickly and accurately in the application they choose, as long as it supports reading and writing XML. Open and royalty-free. The Office XML Formats are based on XML and ZIP technologies, so they are universally accessible. The specification for the formats and schemas will be published and made available under the same royalty-free license that exists today for the Microsoft Office 2003 Reference Schemas, and that is openly offered and available for broad industry use. Interoperable. With industry-standard XML at the core of the Office XML Formats, exchanging data between Microsoft Office applications and enterprise business systems is simplified. Without requiring access to the Office applications, solutions can alter information inside an Office document or create a document by using standard tools and technologies capable of manipulating XML. The new formats enable you to build archives of documents without using Office code. Robust. The Office XML Formats are designed to be more robust than the binary formats, and, therefore, to help reduce the risk of lost information due to damaged or corrupted files.

Even documents created or altered outside of Office are less likely to corrupt, because Office applications are designed to recover documents with improved reliability by using the new formats. With more and more documents traveling through e-mail attachments or removable storage, the chance of a network or storage failure increases the possibility of a document becoming corrupt. The new file formats improve data recovery by segmenting and separately storing each part within the file package. This has the potential to save companies tremendous amounts of money and time spent recovering lost data. When one file component is corrupt, the remainder of the file is still open within the application. For example, if a chart becomes damaged, this does not prevent the customer from opening the other parts of the document, without the chart. In addition, Office applications can detect these defects, and attempt to repair a document when opening it by restoring the proper data structure to the document. Efficient. The Office XML Formats use ZIP and compression technologies to store documents. A significant benefit of the new formats is substantially smaller file sizes—up to 75 percent smaller than comparable binary documents. This is one of the advantages of using the combination of XML and the ZIP technologies for storing files.

Because XML is a text–based format that compresses very well, and the ZIP container supports compressing the contents, users can obtain significant reductions in file size. This type of file compression offers potential cost savings because it reduces the disk space required to store files and decreases the bandwidth needed to transport files through e-mail, over networks, and across the Web. Secure. The openness of the Office XML Formats translates to more secure and transparent files. You can share documents confidently because you can easily identify and remove personally identifiable information and business-sensitive information, such as user names, comments, and file paths. Similarly, you can identify files containing content, such as OLE objects or Microsoft Visual Basic for Applications (VBA) code, for special processing. The file formats also help to improve security against documents with embedded code or macros. By default, the new Word 2007, Excel 2007, and PowerPoint 2007 file formats do not execute embedded code. So, if a person receives an e-mail message with a Word document attached, he or she could open the attachment knowing the document does not execute harmful code.

The Office XML Formats include a special-purpose format with a separate extension for files with embedded code, enabling IT staff to quickly identify files that contain code. Backward-compatible. The 2007 Microsoft Office system is backward-compatible with these earlier versions: Microsoft Office 2000, Microsoft Office XP, and Microsoft Office 2003. Users of these versions can adopt the new format with little effort and continue to gain maximum benefit from existing files. Specifically, they can continue to use the older .doc, .xls, and .ppt binary formats, which are fully compatible with the 2007 file format. Users of earlier Office versions can download a free update that enables them to open and edit files in the new format from within their earlier versions. Users who install the 2007 Office release can set the default file formats to whichever format they choose. This helps ensure that users can continue to work with third-party solutions based on earlier versions, and work with their colleagues, suppliers, customers, and others who have upgraded. Glossary for Office Open XML Formats The following list defines terms used in this article and related content: API A set of functions or methods used to access software functionality.

API is an acronym for application programming interface. Converters Free tools that open files created in the Office XML Formats in previous Office versions. Note The converters read, honor, and apply information rights management (IRM) protection to documents. A document that includes IRM protection continues to be protected regardless of whether the recipient is using the 2007 Office release or a previous version. Forward-compatibility The ability of an earlier version of an application to open files from a later version and ignore features that are not implemented in the earlier version. For example, Word 2003 is forward-compatible with Word 2007 because it can successfully open Word 2007 files using a converter. Office Open XML Formats A structure of building blocks and relationships used for composing, packaging, distributing, and rendering document-centered content. These building blocks define a platform-independent framework for document formats that enable software applications to generate, exchange, and display documents reliably and consistently. Package The ZIP container that holds the components (parts) that comprise the document, as defined by the Open Packaging Conventions specification. Part Corresponds to one file in the package.

For example, if a user right-clicks an Excel 2007 file and chooses to extract it, he or she sees files, such as a workbook.xml file and several sheetn.xml files. Each of those files is a part in the package. Relationships The method used to specify how the collection of parts come together to form a document. This method specifies the connection between a source part and a target resource. Relationships are stored within XML parts (for example, /_rels/.rels) in the document package. XML Extensible Markup Language (XML) is a simple, flexible text format designed for electronic publishing and the exchange of a wide variety of data on the Internet and elsewhere. ZIP An industry-standard compression archives format used to store and transport files between computers, through e-mail, or over the Internet. Structure of the Office XML Formats The new file format container is based on the simple and parts-based compressed ZIP file format specification. At the core of the new Office XML Formats is the use of XML reference schemas and a ZIP container. Each file is comprised of a collection of any number of parts; this collection defines the document. Document parts are stored in the container file or package using the industry-standard ZIP format.

Most parts are XML files that describe application data, metadata, and even customer data, stored inside the container file. Other non-XML parts may also be included within the container package, including such parts as binary files representing images or OLE objects embedded in the document. In addition, there are relationship parts that specify the relationships between parts; this design provides the structure for an Office file. While the parts make up the content of the file, the relationships describe how the pieces of content work together. The results are XML file formats for Office documents that are tightly integrated but modular and highly flexible. The next few sections describe each component of the Office XML Formats in detail. They also describe the Office applications using the new file format. Note To understand the composition of an Office XML Formats file, you might want to extract a file. To open the file, it is assumed that you have a ZIP application, such as WinZip from WinZip Computing Corporation, installed on your computer. To open a Word 2007 XML file Create a temporary folder in which to store the file and its parts. Save a Word 2007 document, containing text, pictures, and other elements, as a .docx file.

Add a .zip extension to the end of the file name. Double-click the file. It will open in the ZIP application. You can see the parts that comprise the file. Extract the parts to the folder that you created previously. ZIP Package Many elements go into creating a Microsoft Office document. Some of these are commonly shared across all the Office applications, for example, document properties, style sheets, charts, hyperlinks, diagrams, and drawings. Other elements are specific to each application, like worksheets in Excel, slides in PowerPoint, or headers and footers in Word. When users save a document with Office 2003 or previous versions of Microsoft Office, a single file is written to disk, which you can easily open. This metaphor is important to how documents are stored, managed, and shared in practice. By wrapping the individual parts of a 2007 Microsoft Office system file in a ZIP container, a document remains as a single file instance. The use of a single package file to represent the entity of a single document means users have the same experience as with previous Office versions when saving and opening Office (2007) documents. They can continue to work with just a single file. Figure 1.

The file format container in the 2007 release With previous Office versions, developers who wanted to manipulate the content of an Office document needed to know how to read and write data according to the structured storage defined within the binary file. This process is complex and challenging, notably because the Office binary file formats were designed to be accessed primarily through the Office applications. The formats reflected the in-memory structures of the applications and could run on low-memory computers with slow hard drives. In addition, altering Office binary files programmatically without the Office applications was identified as a leading cause of file corruption. This deterred some developers from even attempting to alter the files. ZIP was chosen as the package format for the Office XML Formats because it is a well-understood industry standard. There are many tools available today to work with the ZIP format, and using ZIP provides a flexible, modular structure that allows for an expansion of functionality, going forward. Therefore, you have access to the complete contents of 2007 Microsoft Office system documents by using any of the numerous tools and technologies that work with industry-standard ZIP files. After you open a container file, you can manipulate any of the document parts found within the package that define the document.

For example, you can open a Word 2007 document that uses Office XML Formats, locate the XML part that represents the body of the Word document, alter the part by using any technology capable of editing XML, and return the XML part to the container package to create an updated Office document. Parts Within an Office XML Formats package, many logical parts of the file are stored as individual files or parts. This modularity is one of the important characteristics of the file format. Modularity enables you to locate a specific part quickly and to work directly with just that part. You can edit, exchange, or even remove document parts depending on the preferred outcome of a specific business need. All the Office applications share some types of parts, such as the thumbnail, metadata, media, and relationships parts. Others exist consistently within all files as a specific part, such as document properties. Many parts, however, are unique to the application document type they represent. For example, a worksheet part is only found in an Excel document, while a slide master part only appears in a PowerPoint document. It is important to note that, with a few exceptions defined within the Open Packaging Conventions, the actual file directory structure is arbitrary.

The relationships of the files within the package, not the file structure, are what determine file validity. You can rearrange and rename the parts of an Office (2007) XML Formats file inside its ZIP container, provided that you update the relationships properly so that the document parts continue to relate to one another as designed. If the relationships are accurate, the file opens without error. The initial file structure in an Office XML Formats file is the default structure that is created. This default structure enables you to determine the composition of Office XML Formats files easily. Provided that you keep the relationships current, you can change this default file structure. For more information about this, see Walkthrough: Word 2007 Open XML File Format . Parts can be of different content types. Parts used to describe Microsoft Office applications data are stored as XML. These parts conform to the XML reference schema that defines the associated Office feature or object. For example, in an Excel 2007 file, the data that represents a worksheet is found in an XML part that adheres to the Office schema for an Excel worksheet. Additionally, if there were multiple worksheets in the workbook, there is a corresponding XML part stored in the package file for each worksheet.

All of the schemas that represent default Office document parts will be fully documented and made available from Microsoft with a royalty-free usage license. Then, by using any standard XML-based technologies, you can apply your knowledge of the Office schemas to parse and create 2007 Microsoft Office system documents easily. In many scenarios, it is advantageous to store parts in their native content type. These parts are not stored as XML. Images in an Office document in the 2007 release, for example, are stored as binary files (.png, .jpg, and other file types) within the document package. Therefore, you can open the package container by using a ZIP application and immediately view, edit, or replace the image in its native format. Not only is this storage approach more accessible, it also requires less internal processing and disk space than storing an image as encoded XML. Other notable parts stored as binary parts are VBA projects and embedded OLE objects. (Embedded OLE objects are binary only if the associated OLE server provides only a binary representation. 2007 Microsoft Office system–embedded documents, for example, embed their contents as another package.) For developers, accessibility makes many scenarios more attractive.

For example, you can build a solution that iterates a collection of 2007 Microsoft Office system documents to update an existing OLE object with a newer version. You can accomplish this and any number of other scenarios without having to use the Office applications or alter the document-specific XML. The next sections briefly describe some of the parts that are common to all of the Office products that support the Office XML Formats. The types and numbers of parts depend on the application that creates the ZIP container file. For example, Word 2007 creates document-related parts, but PowerPoint 2007 creates parts related to slide presentations. _rels Folder This folder contains a .rels file that defines the root relationships within the package. This is the first place you should go to start parsing through the package. .rels File Contains relationships based on the start part (the virtual start part).

Relationships are defined with the following format: Open XML Formats and file name extensions - Office Support Admin Open XML Formats and file name extensions Applies To: Excel 2013 Word 2013 PowerPoint 2013 Excel 2010 Word 2010 PowerPoint 2010 Excel 2007 Word 2007 PowerPoint 2007 Office 2007 Office 2010 More... Less Starting with the 2007 Microsoft Office system, Microsoft Office uses the XML-based file formats, such as .docx, .xlsx, and .pptx. These formats and file name extensions apply to Microsoft Word, Microsoft Excel, and Microsoft PowerPoint. This article discusses key benefits of the format, describes the file name extensions and discusses how you can share Office files with people who are using earlier versions of Office. In this article Can different versions of Office share the same files? What are the benefits of Open XML Formats? The Open XML Formats include many benefits — not only for developers and the solutions that they build, but also for individual people and organizations of all sizes: Compact files Files are automatically compressed and can be up to 75 percent smaller in some cases.

The Open XML Format uses zip compression technology to store documents, offering potential cost savings as it reduces the disk space required to store files and decreases the bandwidth needed to send files via e-mail, over networks, and across the Internet. When you open a file, it is automatically unzipped. When you save a file, it is automatically zipped again. You do not have to install any special zip utilities to open and close files in Office. Improved damaged-file recovery Files are structured in a modular fashion that keeps different data components in the file separate from each other. This allows files to be opened even if a component within the file (for example, a chart or table) is damaged or corrupted. Better privacy and more control over personal information Documents can be shared confidentially, because personally identifiable information and business-sensitive information, such as author names, comments, tracked changes, and file paths can be easily identified and removed by using Document Inspector. Better integration and interoperability of business data Using Open XML Formats as the data interoperability framework for the Office set of products means that documents, worksheets, presentations, and forms can be saved in an XML file format that is freely available for anyone to use and to license, royalty free.

Office also supports customer-defined XML Schemas that enhance the existing Office document types. This means that customers can easily unlock information in existing systems and act upon it in familiar Office programs. Information that is created within Office can be easily used by other business applications. All you need to open and edit an Office file is a ZIP utility and an XML editor. Easier detection of documents that contain macros Files that are saved by using the default "x" suffix (such as .docx, .xlsx, and .pptx) cannot contain Visual Basic for Applications (VBA) macros and XLM macros. Only files whose file name extension ends with an "m" (such as .docm, .xlsm, and .pptm) can contain macros. Top of Page What are the XML file name extensions? By default, documents, worksheets, and presentations that you create in Office are saved in XML format with file name extensions that add an "x" or an "m" to the file name extensions that you are already familiar with. The "x" signifies an XML file that has no macros, and the "m" signifies an XML file that does contain macros.

For example, when you save a document in Word, the file now uses the .docx file name extension by default, instead of the .doc file name extension. When you save a file as a template, you see the same kind of change. The template extension used in earlier versions is there, but it now has an "x" or an "m" on the end. If the file contains code or macros, you must save it by using the new macro-enabled XML file format, which adds an "m" for macro to the file extension. The following tables list all the default file name extensions in Word, Excel, and PowerPoint. Word Top of Page Can different versions of Office share the same files? Office lets you save files in the Open XML Formats and in the binary file format of earlier versions of Office and includes compatibility checkers and file converters to allow file-sharing between different versions of Office. Opening existing files in Office You can open and work on a file that was created in an earlier version of Office, and then save it in its existing format.

Because you might be working on a document with someone who uses an earlier version of Office, Office uses a compatibility checker that verifies that you have not introduced a feature that an earlier version of Office does not support. When you save the file, the compatibility checker reports those features to you and then lets you remove them before continuing with the save. Opening Office files in earlier versions of Office You can open and change an Office file in Microsoft Word, Excel, or PowerPoint 2003 by downloading the necessary file converters. On the computer that uses an earlier version of Office, go to the Download Center and download the Microsoft Office Compatibility Pack for 2007 Office Word, Excel and PowerPoint File Formats. Important: For the converters to work, the earlier version of Microsoft Office must first be updated to one of the service packs listed here. After you have installed the service pack for your version of Office, download the converter. DOCX - Just Solve the File Format Problem DOCX application/vnd.openxmlformats-officedocument.wordprocessingml.document Office Open XML (OOXML) representation (.DOCX) is the default file format for documents created by Microsoft Word as of Word 2007.

The format is based on XML component files in a container based on the ZIP format. It replaced the binary DOC format used in earlier Word versions, and comes in two flavours, 'strict' and 'transitional' (see below). This format (or the XML components of it) has been referred to as WordProcessingML , a name also used for the standalone XML files the earlier Word 2003 was able to generate. Graphical inserted elements may be stored in the form of DrawingML , embedded in the XML. Contents 6 Other links and references History This (along with the other Office Open XML document types PPTX and XLSX ) was initially standardized as ECMA-376 in 2006. Three versions of ECMA-376 have been produced; the second version corresponds to ISO/IEC 29500:2008, approved as an ISO/IEC standard in April 2008. Changes to the standard between 2008 and 2012 were primarily corrections based on individual defects reported as implementation of the standard proceeded and required to ensure functional interoperability with existing applications. They do not introduce new functionality.

Format High-level structure Like the other "Open XML" formats, this file format actually consists of various files (mostly XML ) compressed into a ZIP archive, with this fact obscured from the end user by the use of a different file extension. Strict versus Transitional The OOXML standard actually defines two different format variations: 'strict' and 'transitional' OOXML. The transitional form is not fully specified within the standard documentation, as it is very closely bound to the specific behaviour of Microsoft Office and the older binary formats. The strict form is the fully standardised form, but Microsoft have been slow to fully support OOXML-Strict as the default format for Office documents, leading to interoperability problems. See this blog post for a more detailed look at the interoperability issues , and here for some context from 2014 concerning government support for open formats . Some more commentary is here . Specs How to: Manipulate Office Open XML Formats Documents How to: Manipulate Office Open XML Formats Documents Collapse the table of content Expand the table of content This documentation is archived and is not being maintained. This documentation is archived and is not being maintained. This documentation is archived and is not being maintained.

How to: Manipulate Office Open XML Formats Documents Office 2007 Summary: Office Open XML Formats files replace legacy binary Office system files. Learn about the components that are included in a formatted file and about several scenarios that show the versatility of these files. (25 printed pages) Frank Rice, Microsoft Corporation Overview In previous versions of Microsoft Office, files created in Microsoft Office Excel, Microsoft Office PowerPoint, and Microsoft Office Word were saved in a proprietary, single file format; they were known as binary files. The 2007 release of the Microsoft Office system introduces new file formats for Microsoft Office Excel 2007, Microsoft Office PowerPoint 2007, and Microsoft Office Word 2007, named the Office Open XML Formats. The Office Open XML Formats are based on XML and ZIP archive technologies. Just as in previous versions of Microsoft Office, documents in the 2007 release are saved in a single file or container so that the process of managing documents stays simple. However, unlike legacy files, Office Open XML Formats files can be opened to reveal component parts that give you access to the structures that compose the file.

In this article, you examine Office Open XML Formats files by manually opening files and exploring each of the parts that make up the document. You also work with the documents programmatically. The files used in this article are available in the download that accompanies this article, 2007 Office System Sample: Manipulating Office Open XML Formats Files . If you do not have access to the download, you can substitute your own program files and image files in the examples. In this section, you examine the XML file format of a sample Word 2007 document that contains text, an image, and properties. To create an Office Open XML Formats document in Word Start Word 2007. In the new document, paste the following text: Soaring with the American Bald Eagle Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Nulla rutrum. Phasellus feugiat bibendum urna. Aliquam lacinia diam ac felis. In vulputate semper orci. Quisque blandit. Mauris et nibh. Aenean nulla. Mauris placerat tempor libero. Pellentesque bibendum.

In consequat, sem molestie iaculis venenatis, orci nunc imperdiet justo, id ultricies ligula elit sit amet ante. Sed quis sem. Ut accumsan nulla vel nisi. Ut nulla enim, ullamcorper vel, semper vitae, vulputate vel, mi. Duis id magna a magna commodo interdum. Highlight the line Soaring with the American Bald Eagle and then, on the Home tab, in the Styles group, set the style to Title. Next, insert an image into the document: Place the cursor at the end of the first paragraph and press Enter to insert a new line. Then, on the Insert tab, click Picture, navigate to an image file (such as the Eagle1.gif file included in the download), and then click Insert. Now add some document properties: Click the Microsoft Office Button, point to Prepare, and then click Properties. In the Document Properties pane, add an author name, title, subject, and comments, as follows: Table 1. Document Property Settings Property Soaring with the American Bald Eagle Subject Description of how Word creates temporary files Description of how Word creates temporary files This article explains when, where, and how Microsoft Word for Windows creates temporary files.

More Information Definition of a temporary file A temporary file is a file that is created to temporarily store information in order to free memory for other purposes, or to act as a safety net to prevent data loss when a program performs certain functions. For example, Word determines automatically where and when it needs to create temporary files. The temporary files only exist during the current session of Word. When Word is shut down in a normal fashion, all temporary files are first closed and then deleted. Why does Word create temporary files? Speed If there is not enough memory available to keep the document with all its edits in memory and still perform manipulations such as sorting, dragging, scrolling, and so on quickly along with any other applications that are running, then Word moves part of its code that is not being used or part of the document that is not being edited from memory to disk. This movement to temporary files on disk frees more memory for text manipulation or storage of the parts of the document that are being actively edited. Data Integrity Word uses temporary files as a "safety net" to protect against system errors in its file-saving scheme.

By saving to a temporary file first and then renaming the file to the proper name, Word ensures the data integrity of your original file against problems (such as a power failure or lost network connections) that may occur while the file is being written. Types of temporary files These are standard MS-DOS files. Document-File-Based File The difference between this file and a traditional MS-DOS file is that multiple programs can read and write to these files without the original owner knowing about it. Additionally, document files have inherent properties that allow Word to create files and directories within files. At startup, Word creates one temporary (direct) document file called ~wrfxxxx.tmp. You can determine that it is a document file because the initial size is 1,536 bytes. This temporary document file is used to store all OLE objects that belong to unnamed documents, Undo, the Clipboard, and documents whose native formats are not document format (for example, .txt, .rtf, and Word 2.0 documents). Word can open document files using two different modes: transacted and direct. These modes are discussed later in this article.

Transacted Document Files Transacted files allow Word to open a file, write to it, and have other programs--such as Microsoft Excel--write to it, but still retain the right to restore the file to the state it was in when Word first opened it. To do this, the document file creates ghost images (typically ~dftxxxx.tmp) of all the changes made to the file after it was opened; if Word keeps all the changes, the contents of ~dftxxxx.tmp merge with the original file, and then saves a complete version of it. Conversely, if Word discards all changes, then ~dftxxxx.tmp is deleted, and the original file does not change. Word opens all of the Word native files using transacted files, which create ghost images in the Temp directory. When you start Word, Normal.dot is typically opened in transacted mode, and a ghost file is created for it called dftxxxx.tmp. FastSave, for example, merges these two files when a save occurs. Direct Word uses direct storage when opening the temporary document file and when performing either a Save As or a Full Save (non-FastSave save).

This type of file is a low (if any) consumer of memory and does not create a ghost image when created or opened. Specific files that Word creates The following tables list some of the specific temporary files that Word creates.

Files typically created when Word is started File name ------------------------------------------------------------------------ MS-DOS-based file (to reserve 4 file handles) 0 bytes ~wrf0000.tmp MS-DOS-based scratch file 0 bytes ~mfxxxx.tmp Compound file - transacted 0 bytes ~dftxxxx.tmp Compound file - direct 1536 bytes ~wrf0001.tmp (unnamed non-Word/OLE files) Word recovery files File name ----------------------------------------------------------------------- Temporary file for AutoRecovery ~wraxxxx.tmp AutoRecovery AutoRecovery save of <docname>.asd Other Word temporary files File name ----------------------------------------------------------------------- Copy of another document ~wrcxxxx.tmp Word document ~wrdxxxx.tmp A simplified view of the scheme used to save an edited file Create temp file Create ~wrdxxxx.tmp Write temp file Save example data to ~wrdxxxx.tmp Delete original file Delete EXAMPLE.DOC Move temp to target name Move ~wrdxxxx.tmp to Example.doc Word gains significant performance speed by placing the temporary file in the same directory as the saved file. If Word placed the temporary file elsewhere, it would have to use the MS-DOS COPY command to move the temporary file from the other directory to the saved location.

By leaving the temporary file in the same directory as the saved document file, Word can use the MS-DOS MOVE command to quickly designate the temporary file as the saved document. When and where Word creates temporary files The location where Word creates the temporary files is hardcoded information and cannot be edited. Therefore, it is important that NTFS permissions for the user are set accordingly. For more information, click the following article number to view the article in the Microsoft Knowledge Base: 277867 Windows NTFS permissions are required when you run Word on any NTFS partition that has Windows 2000, Windows XP Professional, Windows Server 2003, or Windows Vista installed In general, Word creates temporary files for the following types of data. Embedded Word Objects (Temp Directory) When Word acts as an OLE server program, the embedded Word objects are stored as temporary files in the Temp directory. OLE 2.0 requires extra drive storage. When you start OLE programs, Word needs to provide copies of the data to the server. It is not unusual for extensive OLE 2.0 usage in a single session of a program to accumulate a large amount of temporary storage on the hard drive.

Scratch File (Temp Directory) When Word runs out of internal random access memory (RAM), it always creates a single temporary scratch file in the Temp directory to hold information. This scratch file holds information that is swapped out from the Word internal file cache, which is allocated from global system memory. The scratch file varies in size from 64 kilobytes (KB) to 3.5 megabytes (MB). The default cache size in Word is 64 KB. For more information about how to increase the cache size in Word, click the following article number to view the article in the Microsoft Knowledge Base: 212242 Where settings are stored in the registry for Word 2000 Recorded Macro (Temp Directory) When you record a macro, Word creates a temporary file in the Windows Temp directory. Converted Files (Temp Directory) The word processor converters supplied with Word create temporary files in Rich Text Format (RTF), which Word uses to access specific converters. Locked Files (Temp Directory) When you open a file that is locked, either because it is open in another window of Word or because another user on the network has it open, you can work with a copy of the file.

Word places this copy in the Windows Temp directory. Likewise, if a template attached to a document is locked, Word automatically makes a copy of the template in the Temp directory. The copy of a locked file does not automatically update the original owner's file. Saved Files (Same Directory as the Saved File) When you click Save on the File menu, the following happens: Word builds a new temporary file using the edited version of the document. After Word creates the temporary file, Word deletes the previous version of the document. Word renames the temporary file to the same name as the previous version of the document. Text Pasted Between Files (Same Directory as Source File): When Word copies and pastes between documents, it may create a temporary file in the same directory as the source file. This is especially true if the source file is saved or closed. The temporary file represents the information that was referenced by the Clipboard prior to saving the file. Word creates this temporary file by renaming the old copy of the file to a temporary file name. Owner File (Same Directory as Source File) When a previously saved file is opened for editing, for printing, or for review, Word creates a temporary file that has a .doc file name extension.

This file name extension begins with a tilde (~) that is followed by a dollar sign ($) that is followed by the remainder of the original file name. This temporary file holds the logon name of person who opens the file. This temporary file is called the "owner file." When you try to open a file that is available on a network and that is already opened by someone else, this file supplies the user name for the following error message: This file is already opened by user name. Would you like to make a copy of this file for your use? Word may be unable to create an owner file. For example, Word cannot create an owner file when the document is on a read-only share. In this case, the error message changes to the following error message: This file is already opened by another user. Would you like to make a copy of this file for your use? Note Word automatically deletes this temporary file from memory when the original file is closed. When you open a file by using the HTTP or FTP protocol, the file is first copied to the temp directory. Then, the file is opened from the temp directory. When you open a file on a UNC share with Word 2007, the file is first copied to the temp directory.

Then, the file is opened from the temp directory. Automatic Save Word Auto Recover Save Directory The temporary file that is created when Word performs an automatic save is stored in the Temp folder, unless there is not a valid Temp folder. In this case, Word saves the temporary file in the same folder where it saves the document. The location of temporary files when you close a file Word may occasionally have to maintain a link to a file after it is closed. This occurs when text has been copied to the Clipboard from the file. When you close a file, Word attempts the following actions: If the selection that was copied to the Clipboard does not contain multiple sections or a picture, or is not large, Word copies the piece of the document to the scratch file. If the copied selection does contain pictures or multiple sections, or if the file is on a floppy disk, Word copies the entire file to the Temp directory and moves the pointer there. Properties XML file name extension reference for Office 2013 Collapse the table of content Expand the table of content This documentation is archived and is not being maintained. This documentation is archived and is not being maintained.

XML file name extension reference for Office 2013 Office 2013 Applies to: Office 365 ProPlus, Office 2013 Topic Last Modified: 2014-03-14 Summary: Learn about the XML file formats and their extensions that are used by Word 2013, Excel 2013, PowerPoint 2013, and Visio 2013. Audience: IT Professionals XML file formats and their extensions are listed in the following tables for Word 2013, Excel 2013, PowerPoint 2013, and Visio 2013. Important: This article is part of the Content roadmap for Office 2013 compatibility . Use the roadmap as a starting point for articles, downloads, scripts, and videos that help you assess Office 2013 compatibility. Are you looking for information about opening and saving Office documents in different file formats? You can find this information by searching for "2013 file format" on Office.com . In this article: The following table describes the file type, extension, and description for Word XML file formats.

XML file types for Word 2013 Word 2013 file type The default Word file format. Can't store VBA macro code. Strict Open XML document .docx Conforms to the Strict profile of the Open XML standard (ISO/IEC 29500). This profile of Open XML doesn't allow a set of features that were designed specifically for backward-compatibility with existing binary documents, as specified in Part 4 of ISO/IEC 29500. Word Macro-Enabled Document .docm Uses the same basic XML format as the Word document format, but can store VBA macro code. This file type is created when VBA macro code is present in the file. Word Template .dotx The default format for a Word template. Created when document styles and formatting are saved. Can't store VBA macro code. Word Macro-Enabled Template .dotm Stores macro code for use with other Word documents. Does not always contain macro code, but is configured to support the storage of macro code. Word documents created from a macro-enabled template do not inherit the VBAProject part of the template.

By default, documents are saved as .docx files even when they are created from a Word macro-enabled template. The following table describes the file type, extension, and description for Excel XML file formats. XML file types for Excel 2013 Excel 2013 file type Excel Workbook .xlsx The default Excel file format. Can't store VBA macro code or Microsoft Excel 4.0 macro sheets (.xlm files in Excel 4.0). Strict Open XML Spreadsheet An ISO strict version of the Excel Workbook file format (.xlsx). Excel Macro-Enabled Workbook .xlsm Uses the same basic XML format as the Excel Workbook, but can store VBA macro code. Users who save an Excel workbook that has VBA code or Excel 4.0 macro sheets (.xlm files in Excel 4.0) are prompted to use this file format. Excel Template .xltx The default file format for an Excel template. Can't store VBA macro code or Excel 4.0 macro sheets (.xlm files in Excel 4.0). Excel Macro-Enabled Template .xltm Can contain a VBAProject part or Excel 4.0 macro sheets (.xlm files in Excel 4.0).

Workbooks created from this template inherit the VBAProject part or Excel 4.0 macro sheets that exist in the template. Excel Add-In .xlam A supplemental program that runs additional code. Excel add-ins use the Open XML file format to store data, and they support using VBA projects and Excel 4.0 macro sheets. The following table describes the file type, extension, and description for PowerPoint XML file formats. XML file types for PowerPoint 2013 PowerPoint 2013 file type PowerPoint Presentation .pptx The default PowerPoint XML format. Can't contain a VBAProject part (the part that stores VBA macro code) or Action settings. Strict Open XML Presentation An ISO strict version of the PowerPoint Presentation file format (.pptx). PowerPoint Macro-Enabled Presentation .pptm The same basic XML format as the PowerPoint XML presentation format, but can store VBA macro code. Users who save a PowerPoint XML presentation file that contains VBA macro code are prompted to use this file type. PowerPoint Template .potx An XML-based PowerPoint template. Created when a presentation does not have a VBAProject part and does not use Action settings.

PowerPoint Macro-Enabled Template .potm Users who save a PowerPoint XML template that contains VBA macro code are prompted to use this file type. Presentations created from this template do not inherit the VBAProject part or Action settings. PowerPoint Add-In PowerPoint presentation designed to be run as a supplemental program. All PowerPoint add-ins are macro-enabled. PowerPoint Show An XML-based PowerPoint auto-running slide show. Can't contain a VBAProject part. PowerPoint Macro-Enabled Show .ppsm An XML-based PowerPoint slide show file that contains a VBAProject part. Created when the auto-running slide show includes VBA macro code. The following table describes the file type, extension, and description for Visio XML file formats. Note: Visio 2013 uses the XML file format package that is defined by the Open Packaging Conventions (ISO/IEC 29500-2:2008) standard. The XML content is based on the existing Visio XML Drawing (VDX) format. XML file types for Visio 2013 Visio 2013 file type The default Visio 2013 file format. Can't store VBA macro code.

Visio Macro-Enabled Drawing .vsdm Uses the same basic XML format as the Visio drawing format (.vsdx), but can store VBA macro code. This file type must be used when VBA macro code is present in the file. Visio Stencil The default format for a Visio 2013 stencil. Can't store VBA macro code. Visio Macro-Enabled Stencil .vssm Uses the same basic XML format as the Visio Stencil (.vssx) format, but can store VBA macro code. Does not always contain macro code, but is configured to support the storage of macro code. Visio Template The default format for a Visio 2013 template. Can't store VBA macro code. Visio Macro-Enabled Template .vstm Uses the same basic XML format as the Visio Template (.vstx) format, but can store VBA macro code. Does not always contain macro code, but is configured to support the storage of macro code. Visio Drawings that are created from this template inherit the VBAProject part that exists in the template.

However, by default, drawings are saved as .vsdx files even when they are created from a Visio macro-enabled template and will drop the VBAProject part.

Question: Which component of Microsoft Office generates files with a .doc or .docx file suffix?
Answer: WORD