xmllint --xpath "//item/name" inventory.xml > output.txt xmllint --noblanks document.xml --output minified.xml Real-World Examples for Windows Users Example 1: Batch Validate All XML Files in a Folder In PowerShell or cmd:
xmllint --xpath "//book/title" library.xml To save the result to a file:
xmllint --format ugly.xml --output pretty.xml xmllint --valid --noout document.xml Or, explicitly using a DTD file: xmllint windows
[xml]$xml = Get-Content .\file.xml $xml.SelectNodes("//book/title") | ForEach-Object $_.InnerText However, xmllint remains far superior for validation, formatting, and XPath 1.0 support. xmllint brings enterprise-grade XML processing to the Windows command line. While the initial setup requires downloading a few binaries or using WSL, the investment pays off immediately for developers, DevOps engineers, and data analysts who work regularly with XML. Whether you need to validate a configuration file, reformat messy output, or script data extraction, xmllint is an indispensable tool.
xmllint --xpath "string(//database/@host)" config.xml Output: localhost Because xmllint works with standard input, you can chain commands: xmllint --xpath "//item/name" inventory
xmllint --dtdvalid schema.dtd document.xml xmllint --schema myschema.xsd --noout data.xml 5. Extract Data with XPath The --xpath option is extremely useful for querying XML:
type ugly.xml | xmllint --format - > formatted.xml (The - tells xmllint to read from stdin.) | Error | Likely Cause | Solution | |-------|--------------|----------| | 'xmllint' is not recognized | Not in PATH | Re-check PATH variable or restart terminal. | | error : Could not find DTD | Missing DTD file | Use absolute paths: xmllint --dtdvalid C:\schemas\file.dtd | | Failed to load external entity | Network DTD blocked | Download DTD locally or use --nonet to skip network. | | iconv.dll not found | Missing dependency | Copy iconv.dll from the Zlatkovic package into the same folder as xmllint.exe . | Alternative: Using PowerShell’s Native XML For Windows users who cannot install third-party tools, PowerShell has built-in XML capabilities: Whether you need to validate a configuration file,
for %f in (*.xml) do xmllint --noout "%f" (Use %%f inside a batch file) Suppose config.xml contains: