Introduction
If you still see charges on your Runpod account after stopping pods or services, it is usually because some resources are still allocated or because stopped pods continue to incur storage charges. This article explains the most common billing reasons, how stopping differs from terminating or deleting a pod, and how to review your current usage so you can avoid unexpected charges.
Why charges can continue after stopping a pod
Stopping a pod does not remove all associated resources. In most cases, the pod's storage remains attached, and that storage continues to be billed even when the GPU is no longer running. If the pod is still active in any way, or if a service is still deployed, you may also see additional usage-related charges.
Storage charges for stopped pods
Stopped pods continue to incur storage charges at $0.20 per GB per month. This applies because the data volume remains provisioned even though the pod is not running.
Storage charges for running pods
Running pods are billed for storage at $0.10 per GB per month. In addition to storage, running pods also incur GPU charges while the pod is active.
GPU charges while pods are running
GPU usage is billed only while a pod is running. If a pod is not fully stopped or if it is restarted automatically, GPU charges may continue to appear on your account.
Stopping vs. terminating or deleting a pod
Stopping a pod pauses compute usage, but it does not necessarily remove the pod's storage or configuration. Terminating or deleting a pod removes the resource entirely, which is the best way to stop storage-related billing if you no longer need the pod or its data.
Use stopping when you plan to resume work later and want to keep the pod available. Use terminating or deleting when you want to prevent ongoing charges for resources you no longer need.
User responsibility for accidental charges
Users are fully responsible for monitoring and managing their own resources. If pods or storage are left running or allocated — whether intentionally or accidentally — the resulting charges are the user's responsibility. Runpod does not cover, waive, or reimburse charges for resources that were left running or allocated by the user.
To avoid unexpected charges, it is important to regularly review your active pods, services, and storage volumes, and to terminate or delete any resources you no longer need.
How to avoid unexpected charges
- Terminate or delete pods you no longer need.
- Review attached storage volumes and remove any that are no longer required.
- Confirm that no services or workloads are still running in the background.
- Check for pods that may have restarted automatically or were left active in another region or workspace.
- Set a regular schedule to review active resources and billing activity.
How to check current resource usage and billing
To understand what is driving your charges, review both your active resources and your billing details in the Runpod dashboard.
- Sign in to your Runpod account.
- Open the Pods or Services section to see what is currently running, stopped, or still provisioned.
- Check each pod for attached storage size and status.
- Review your charges directly on the Runpod billing page to see charges by resource type, including GPU and storage usage.
- Compare the billing entries with your active resources to identify any pod or volume that is still generating charges.
Summary
Charges can continue after stopping pods because storage remains allocated, and stopped pods are billed at $0.20 per GB per month. Running pods are billed at $0.10 per GB per month(prices may change and should be checked while creating the resources) for storage and also incur GPU charges while active. To avoid unexpected billing, terminate or delete resources you no longer need and regularly review your usage and billing in the Runpod dashboard.
Additional information
If you still cannot identify a charge, review all workspaces, regions, and attached volumes associated with your account. If needed, contact Runpod support with the relevant pod names, timestamps, and billing details for further investigation.