Skip to main content
Pod-based indexes are legacy. Customers who signed up for a Standard or Enterprise plan on or after August 18, 2025 cannot create them. Create a serverless index instead. Serverless indexes use on-demand read capacity by default, or dedicated read nodes for sustained high query rates and workloads of millions of records or more.
SDKs that target API version 2026-07 don’t support creating pod-based indexes, and they reject creating an index from a collection. You can still list, describe, and delete existing collections. To create or restore a pod-based index, use an SDK version that targets an earlier API version, or send an earlier X-Pinecone-Api-Version with the REST API. To move a pod-based index to serverless, see Migrate a pod-based index to serverless.
You can restore a pod-based index by creating a new index from a collection.

Create a pod-based index from a collection

To create a pod-based index from a collection, use the Create an index endpoint and provide a source_collection parameter containing the name of the collection from which you wish to create an index. The new index can differ from the original source index: the new index can have a different name, number of pods, or pod type. The new index is queryable and writable.