# Redoc vs Powerduck API Reference

**Short answer:** Redoc is a mature, respected reference renderer; a studio-generated reference is the contract rendered and kept in sync with the surfaces you develop against. The first is a strong standalone renderer; the second shares the source with debug, test, and mock.

## What Redoc is built for

A clean, three-panel reference from an OpenAPI file. It is a good choice when the reference is the deliverable and the rest is handled elsewhere.

## What a generated reference shares

| Property | Redoc | Studio reference |
| --- | --- | --- |
| Renderer | Mature | Generated |
| Source | OpenAPI file | Same spec |
| Other surfaces | Separate | Shared |
| Drift | As configured | Not possible |

## Why the shared source matters

A standalone renderer is correct for the file it is given, but it does not connect to the mocks and tests. A studio keeps the reference and the development surfaces on the same contract.

## The decision rule

Use Redoc when you want a proven renderer and handle the rest separately. Use the studio when the reference and the other surfaces should always agree.

This is part of the [Powerduck vs Redocly comparison](https://www.powerduck.com/blog/powerduck-vs-redocly/). Next, read [the CLI comparison](https://www.powerduck.com/blog/redocly-cli-vs-openapi-cli/).