Formatting Output

PowerShell deliberately separates the objects flowing through a pipeline from the way they are displayed on screen; formatting is applied only at the very end, right before output reaches the console, a file, or another destination. This separation means the same underlying object can be rendered as a table, a list, or a custom view without ever changing the object itself, which is why formatting cmdlets should always be the last stage in a pipeline.

Format-Table renders objects as aligned columns, ideal for scanning many objects at once, while Format-List prints one property per line, better suited to inspecting a single object's full detail. Both accept explicit property names to control which columns or fields appear and in what order, and Format-Table supports -AutoSize to size columns to their content or -Wrap to wrap long values instead of truncating them.

Format-Wide prints a single property across multiple columns in a compact grid, useful for long simple lists like file names. Any Format-* cmdlet also accepts a calculated property expressed as a hashtable @{ Label = 'DisplayName'; Expression = { $_.SomeCalculation } }, letting you show a derived value, such as a computed percentage or ratio, as if it were a real property.

Beyond formatting for the console, PowerShell offers dedicated Out-* cmdlets: Out-GridView opens an interactive, sortable, filterable window (on platforms where it's available), Out-File writes text to disk, and Out-String collapses formatted output into a single string. For actually exchanging data with other systems, ConvertTo-Json, ConvertTo-Csv, and ConvertTo-Html serialize the underlying object data itself, which is fundamentally different from formatting it for human eyes.