Does it look inside nested folders?

Yes, it recurses through the entire item tree, however deeply folders are nested, and every request found anywhere in that tree is counted, not just top-level ones.

How does it determine a request's 'host'?

It reads the url.host array Postman stores (joined with dots) when present, or parses url.raw otherwise. A host that starts with a {{variable}}, like {{baseUrl}}, is reported as that variable name rather than a resolved domain, since the actual value lives in an environment, not the collection.

What counts as a 'script'?

Only pre-request and test events whose script.exec array actually contains non-empty code. An event block that exists but has no real code in it (a common leftover from deleting a script's contents) doesn't count.

Postman Collection Analyzer - Summarize a Collection Online

Overview

Introduction

A large Postman collection accumulated over time, with folders inside folders, mixed auth types, and scripts scattered across requests, can be hard to get a quick overview of just by scrolling through it.

This tool walks the entire structure and produces a summary: how many requests, which methods, which auth types, and how many carry scripts, entirely in your browser.

What Is Postman Collection Analyzer?

An analyzer that recursively walks a Postman Collection v2.x's item tree and tallies up structural facts about it, rather than transforming the collection itself.

It's part of this site's API Tools collection and runs entirely client-side.

How Postman Collection Analyzer Works

Every entry in the item tree is checked: if it has its own nested item array it's counted as a folder and recursed into, otherwise it's treated as a request and its method, host, auth type, and scripts are tallied.

The collection's own top-level variable array length is reported separately from anything found inside individual requests.

When To Use Postman Collection Analyzer

Use it when you've inherited a large collection from someone else and want a quick sense of its shape before working with it.

It's also useful for spot-checking that a collection's auth setup and scripts are consistent before converting it or sharing it with a team.

Often used alongside Postman to OpenAPI Converter.

Features

Advantages

Recurses through arbitrarily nested folders, so no request is missed regardless of how the collection is organized.
Distinguishes {{variable}}-based hosts from resolved domains, matching how Postman collections are actually structured around environments.

Limitations

Doesn't inspect the actual content of pre-request or test scripts, only whether they're present.
Auth type reporting reflects each request's own auth block; collection- or folder-level auth inheritance isn't resolved down to each request.

Examples

Summarizing a small collection

Input

A collection with 12 requests across 3 folders, 9 using bearer auth and 3 using none

Output

Requests: 12 · Folders: 3 · GET: 5, POST: 6, DELETE: 1 · Auth types: bearer, noauth

Every request in every folder is counted once, grouped by method and by the auth type its own request block declares.

Spotting variable-based hosts

Input

url.raw: "{{baseUrl}}/v1/users"

Output

Unique hosts: {{baseUrl}}

Since the host starts with a Postman variable rather than a literal domain, it's reported as the variable name, not resolved to an actual URL.

Best Practices & Notes

Best Practices

Run this before converting a collection to OpenAPI, so you know upfront how many auth types and hosts the converter will need to handle.
Use the folder count as a sanity check that your organizational structure matches what you expect after a team member edits the collection.
Treat a high 'noauth' count as a prompt to check whether those requests are actually meant to be unauthenticated.

Developer Notes

A request is identified as any item lacking its own `item` array but carrying a `request` field (object or, per the schema, occasionally a bare URL string); anything else is treated as a folder and recursed into, matching how the Postman Collection v2.1 schema itself distinguishes the two item shapes.

Postman Collection Analyzer Use Cases

Getting a quick overview of an inherited or third-party Postman collection before working with it
Auditing how many requests use each auth type across a large collection
Checking whether pre-request or test scripts are actually present before relying on them in CI

Common Mistakes

Assuming folder-level or collection-level auth is reflected per-request; this tool only reports each request's own auth block.
Expecting script content itself to be checked; only presence of non-empty script code is tallied.

Tips

If 'unique hosts' shows more entries than you expect, check for a mix of {{variable}}-based and hardcoded URLs across the collection.

Postman Collection Analyzer