PowerShell Write to CSV: A Practical Guide
Learn how to write data to CSV using PowerShell with Export-Csv, ConvertTo-Csv, and robust patterns for encoding, appending, and data transformation. This guide covers real-world workflows for developers and analysts, including handling headers, delimiters, and large datasets.
PowerShell writes data to CSV primarily with Export-Csv. Create or retrieve objects, then pipe them to Export-Csv with -NoTypeInformation to avoid type headers. Use -Append to add rows, -Encoding utf8 for portability, and -Delimiter ';' for different locales. For quick transformation, ConvertTo-Csv returns CSV text without writing to a file.
Overview: Writing to CSV with PowerShell
In this guide, we explore how to perform powershell write to csv, demonstrating how to convert objects into CSV data and how to control the output with common parameters. MyDataTables audience of data analysts and developers relies on practical, copy-paste-ready patterns; this article delivers those patterns with real examples. We begin with a mental model: collect or create a collection of PowerShell objects, pipe that collection to an exporter, and let the exporter emit a CSV text with a header row by default. You can tailor encoding, delimiter, and header presence. We'll cover appending to existing files and streaming large datasets to avoid heavy memory use. By mastering these patterns, you can move data from PowerShell pipelines into CSV-based workflows across Windows and cross-platform environments.
# Create sample data as PSCustomObjects
data = @(
[pscustomobject]@{ Name = "Alice"; Department = "Finance"; Salary = 76000 },
[pscustomobject]@{ Name = "Bob"; Department = "Engineering"; Salary = 90000 }
)
# Write to CSV without type information header
$data | Export-Csv -Path "./employees.csv" -NoTypeInformationParameters and outcomes:
- The objects become rows in the CSV, with property names as headers.
- -NoTypeInformation suppresses the extra PSObject type header.
Common variations:
- Use Select-Object to pick only certain fields before exporting.
- Combine multiple pipelines for transformation before export.
Steps
Estimated time: 30-45 minutes
- 1
Install and verify PowerShell
Ensure PowerShell 7.x is installed and accessible from your terminal. Run pwsh -Command '$PSVersionTable.PSVersion' to verify the version. This ensures compatibility with cmdlets like Export-Csv and ConvertTo-Csv.
Tip: Use the copy-paste of the install commands from the official docs to avoid version mismatches. - 2
Create sample data
Create a collection of objects to export. This mirrors real-world data you might pull from a system or API.
Tip: Use PSCustomObject to define strongly-typed fields for predictable CSV headers. - 3
Export to CSV with headers
Pipe your object collection to Export-Csv, using -NoTypeInformation to keep the CSV clean.
Tip: Include -Encoding utf8 when exporting to ensure cross-platform compatibility. - 4
Append data to an existing file
When you need to grow an existing dataset, use -Append and avoid rewriting headers.
Tip: Remember that the first write creates headers; subsequent appends should not re-write headers. - 5
Handle encoding and delimiters
Control encoding or delimiter to adapt to different locales and systems.
Tip: For locales expecting semicolons, use -Delimiter ';'. - 6
Validate and read back
Import the CSV back to confirm the export results and inspect the header and rows.
Tip: Use Import-Csv with Format-Table for quick visual validation.
Prerequisites
Required
- Required
- Required
- Basic PowerShell knowledge (pipelines, objects, and Cmdlets)Required
- Read/Write permissions for source and destination CSV filesRequired
Optional
- Optional: UTF-8 encoding awareness for cross-platform portabilityOptional
Commands
| Action | Command |
|---|---|
| Export objects to CSVOutputs a standard CSV with a header row | Get-Process | Export-Csv -Path './processes.csv' -NoTypeInformation |
| Append new rows to an existing CSVAppends rows to the file; headers are preserved from the first write | Get-Process | Export-Csv -Path './processes.csv' -NoTypeInformation -Append |
| Convert objects to CSV textUseful when embedding CSV data in messages or logs | Get-Process | Select-Object Name,Id,CPU | ConvertTo-Csv -NoTypeInformation |
| Import CSV and filterRead and filter existing CSV data | Import-Csv -Path './processes.csv' | Where-Object { $_.CPU -gt 100 } |
People Also Ask
What is the difference between Export-Csv and ConvertTo-Csv?
Export-Csv writes the data to a file, including headers. ConvertTo-Csv formats objects as CSV text without saving to disk, which is useful for embedding in messages or logs.
Export-Csv saves to a file with headers; ConvertTo-Csv gives you CSV text you can reuse in other contexts.
Can Export-Csv handle large CSV files without excessive memory use?
Yes, when dealing with large datasets, build objects progressively and pipe them to Export-Csv, possibly using ForEach-Object to stream data and avoid loading everything into memory at once.
Yes—stream data and incrementally export to CSV to avoid memory spikes.
How do I export with a delimiter other than a comma?
Use the -Delimiter parameter to specify a different separator, such as a semicolon, which improves compatibility with locales that expect non-comma CSV formats.
You can switch delimiters with -Delimiter to match regional formats.
How do I preserve headers when appending data to an existing CSV?
Headers are written on the first Export-Csv call. When appending, use -Append and ensure your data structure matches the original headers.
First write creates headers; subsequent appends reuse the headers.
Is it possible to export from JSON or other sources to CSV with PowerShell?
Yes. ConvertFrom-Json or ConvertFrom-Json on a JSON string/object, then pipe the resulting objects to Export-Csv to generate a CSV file.
You can convert JSON to objects and then export to CSV easily.
Main Points
- Export-Csv creates CSV files from PS objects
- Use -NoTypeInformation to keep headers clean
- Use -Append to extend existing CSVs
- Control encoding and delimiter for portability