Transloadit
Pricing
  • Handling uploads
  • File importing
  • Video encoding
  • Audio encoding
  • Image processing
  • Artificial intelligence
  • Document processing
  • File filtering
  • Code evaluation
  • Media cataloging
  • File compressing
  • File exporting
  • Smart CDN
  • Explore live demos
  • Uppy
  • TransloaditKit
  • Android SDK
  • Node SDK
  • Python SDK
  • Ruby SDK
  • Go SDK
  • Zapier
  • MCP Server
  • Terraform
  • Essentials
  • Best Practices
  • FAQ
  • Robots
  • API
  • Formats
  • Build your first app
  • About
  • Open Source
  • Testimonials
  • Jobs
  • Security
  • Posts
  • DevTimes
  • DevTips
  • Press
  • Case Studies
  • Solutions
  • Comparisons
  • Guides
  • Glossary
  • Legal
  • Tools
  • Helping Coursera bring education to millions around the world
  • Transloadit Support
  • Open Source Support
  • Service level agreement
EssentialsRobotsFAQAPIFormatsBest Practices

Why are there /meta/read charges in my billing?

The /meta/read charges appear in your monthly billing, because Transloadit by default automatically extracts metadata from your uploaded files and other Steps. This is a standard part of file processing that helps enable features like using ${file.ext}, ${file.name}, and other metadata variables in your Assembly Instructions.

How much do /meta/read charges cost?

Metadata extraction costs 1% of the file size. For example:

  • A 100 MB file would incur 1 MB in metadata extraction charges
  • A 1 GB file would incur 10 MB in metadata extraction charges

How can I avoid /meta/read charges?

You can opt out of automatic metadata extraction by adding "output_meta": false to your processing Step:

{
  "steps": {
    ":original": {
      "robot": "/upload/handle",
      "output_meta": false
    },
    "resize": {
      "use": ":original",
      "robot": "/image/resize",
      "format": "jpg",
      "width": 200,
      "height": 200,
      "output_meta": false
    }
  }
}

When should I keep metadata extraction enabled?

Most processing Templates will require meta data extraction. It's important for:

  • letting Robots ignore file types they cannot handle
  • using file metadata variables in your Assembly Instructions (like ${file.ext}, ${file.name}, ${file.meta.width})
  • filtering files based on metadata properties
  • storing metadata tags with your files
  • generating dynamic file paths based on file properties

Example that may not require metadata:

{
  "steps": {
    ":original": {
      "robot": "/upload/handle"
    },
    "stored": {
      "use": ":original",
      "robot": "/s3/store",
      "path": "/uploads/${file.id}_${file.name}"
    }
  }
}

When can I safely disable metadata extraction?

You can disable metadata extraction when:

  • You don't use any file metadata variables in your Assembly
  • You're using fixed file paths and names
  • You don't need to filter or sort files based on their properties

Example that doesn't need metadata (fields is provided when creating the Assembly):

{
  "steps": {
    "uploaded": {
      "robot": "/upload/handle",
      "output_meta": false
    },
    "exported": {
      "use": "encoded",
      "robot": "/s3/store",
      "path": "${fields.output_path}"
    }
  }
}

See also:

What are Collaboration Seats?
What are priority slots?
How do I enable multi-file upload?
TransloaditChecking status…

Product

  • Services
  • Pricing
  • Demos
  • Tools
  • Security
  • Support

Company

  • About/Press
  • Blog/Jobs
  • Comparisons
  • Open source
  • Solutions

Docs

  • Getting started
  • Transcoding
  • FAQ
  • API
  • Supported formats

More

  • Platform status⁠
  • Community forum⁠
  • StackOverflow⁠
  • Uppy
  • tus⁠

© 2009–2026 Transloadit-II GmbH

PrivacyTermsImprint