Query folding
Translating Power Query steps into the source's own query language (often SQL) so the source does the work.
Folding matters most with databases: filters and column selections that fold are executed by the server, so only the needed rows travel. Some steps, such as adding an index or using certain custom functions, stop folding for every step after them. Files like CSV never fold.
In the Power Query editor
Right-click a step: View Native Query is available when that step folds. Step folding indicators show the same.
Common mistake
Adding a step that breaks folding early in a query against a large database, then wondering why refresh slows down. After a non-folding step, every later filter and column choice runs on your machine, so the whole table has to be downloaded first. Put filters, column removals and joins that fold at the top of the query, check View Native Query or the folding indicators after each step, and move steps such as an index column or a custom function call as late as you can. Folding also depends on the connector: a step that folds against one database may not fold against another source, so check each query rather than assuming.