Collections and folders

A collection is the top-level container in Rewind. It holds folders, and folders hold requests (and other folders). Every saved request lives inside exactly one collection.

This page covers the everyday actions on collections and folders: create, rename, move, duplicate, delete, and export.

Creating a collection

There are two ways:

• Click the + button next to the Collections header in the sidebar. Type a name. Done.
• If you have no collections yet, click the dashed Create a collection to save your first request placeholder in the sidebar.

The new collection appears at the bottom of the Collections section. It is automatically selected, and the URL bar's environment picker is unchanged.

Creating a folder

Folders are always created inside a collection or another folder. Two entry points:

• From a collection's overflow menu, click New folder. The new folder is created at the collection root.
• From a folder's overflow menu, click New subfolder. The new folder is created as a child of the selected folder.

Type a name. Folders can be renamed later.

Renaming, duplicating, deleting

Every collection, folder, and request has an overflow menu (... button) that shows the relevant actions.

Action	Collection	Folder	Request
New folder / subfolder	yes	yes	—
New request	yes (button in row)	yes (button in row)	—
Run collection	yes	—	—
Export Postman	yes	—	—
Rename	yes	yes	yes
Duplicate	yes	yes	yes
Move	—	yes	yes
Delete	yes	yes	yes

Destructive actions (Delete) are colored red. The confirmation dialog explicitly warns that the action permanently removes the item and its children.

What deletion does

• Deleting a collection deletes every folder and request inside it. The action is permanent; there's no undo. The dialog names the collection.
• Deleting a folder deletes the folder and all subfolders, and moves the requests in it to the folder's parent (collection root if the folder was at the top). Their folderId is set to null server-side.
• Deleting a request removes the request and the history entries that reference it (those entries still exist; their requestId becomes null).

What duplication does

• Collection duplication copies the collection, all its folders, and all its requests. The copy is named <original> copy. IDs are fresh; nothing is shared with the original.
• Folder duplication copies the folder, its subfolders, and the requests in it. The copy is placed next to the original in the parent.
• Request duplication creates a copy named <original> copy in the same folder. Environment bindings, headers, body, and auth are all preserved.

Moving with drag and drop

Folders and requests can be moved by dragging them:

• Drag a request onto a folder row to nest it inside that folder.
• Drag a folder onto another folder row to nest it as a subfolder.
• Drop on the collection row (the row with the collection's name) to bring the item back to the collection root.
• Drop on the empty area below all folders in a collection to bring the item to the root as well.

You can only drag within a single collection. To move an item between collections, use the Move action in the menu (it presents a destination-folder picker for the same collection only — cross-collection move is not yet supported).

The server normalizes the tree order after every move. sortOrder is rewritten to be a contiguous 0..n-1 sequence so that what you see is what is stored.

Exporting a collection to Postman

A single collection can be exported as a Postman v2.1 JSON file. From the collection's overflow menu, click Export Postman. A file named <collection>.postman_collection.json is downloaded.

What gets exported:

• Collection name and description
• Folder nesting and names
• Request name, method, url, headers, query params, raw body, URL-encoded body
• Auth configuration

What does not get exported:

• Multipart file uploads (the file references survive as IDs, but the files themselves are not bundled in the Postman export)
• Binary bodies
• Attachment-backed network settings (CA, client cert, key)
• Environment variables
• History
• Secrets are exported as-is in this format; Rewind does not redact them when targeting Postman

To back up everything, use the .rewind archive instead.

Sorting

Within a folder, requests are sorted by sortOrder, then by creation time. Within a collection's root, the same applies. Drag-and-drop moves update sortOrder automatically.

What's next?

• Saving and tabs — the per-request save state and how conflicts are handled
• Running a collection — execute every request in order
• Importing OpenAPI — generate a collection from a spec