Example usage of Export-Csv.
Get-Process | Select-Object Name, Id | Export-Csv .\processes.csv -NoTypeInformationExport-Csv cmdlet
Converts objects into a series of character-separated value (CSV) strings and saves the strings to a file.
Syntax
Export-Csv [-Path] <string> [-NoTypeInformation]This is a practical syntax summary, not every parameter set. Run Get-Command Export-Csv -Syntax and Get-Help Export-Csv -Full in the installed version for its complete syntax and parameter metadata. Common parameters and -WhatIf/-Confirm support depend on the command and PowerShell version.
Examples
Read all available parameter sets and help for the installed module.
Get-Help Export-Csv -FullParameters, options and clauses
| Option / clause | Description |
|---|---|
-Path <file> | Choose the output file. |
-NoTypeInformation | Omit the PowerShell type-information row. |
-Delimiter <char> | Set the column delimiter. |
-Append | Append rows to an existing file where supported. |
-Encoding <name> | Set output encoding where supported. |
-Verbose | Write additional diagnostic detail to the verbose stream. |
-Debug | Write debugging messages to the debug stream. |
-ErrorAction <action> | Control how a non-terminating error is handled. |
-ErrorVariable <name> | Store error records in a variable. |
-WarningAction <action> | Control how warnings are handled. |
-WarningVariable <name> | Store warning messages in a variable. |
-InformationAction <action> | Control how information messages are handled. |
-InformationVariable <name> | Store information messages in a variable. |
-OutVariable <name> | Store output in a variable as well as sending it onward. |
-OutBuffer <count> | Set the number of objects to collect before the next command runs. |
-PipelineVariable <name> | Store the current pipeline object in a variable during processing. |
-ProgressAction <action> | Control progress reporting in versions that support this parameter. |
-WhatIf / -Confirm | Risk-control parameters available only on commands that support ShouldProcess. |
Related PowerShell references
Review a command and its target before running it. Commands that alter files, services, accounts, disks, permissions or databases may be difficult to reverse. Test in a safe environment and keep backups.