Be the first to get access to new connectors. Get early access →
ConnectorBay Early access
Discover
Video Codec Guide icon

Video Codec Guide

H.264/H.265/ProRes/AV1 and container tradeoffs, file-size math, and YouTube's own bitrate table

Unify Dynamics LLC

Documentation
Tools9read-only
Sign-inNoneno account, no key
Data keptNoneprocessed in memory
PriceFreeoptional Pro limits
StatusLiveMCP + REST
Works withMCP · RESTany agent

Try asking

Real questions, and the tools your agent calls to answer them.

What's the difference between H.264 and H.265?
Tools called
codec_info
What codecs do you cover?
Tools called
list_codecs
MP4 vs MOV for delivery
Tools called
container_info
What container formats do you cover?
Tools called
list_containers
File size of a 50 Mbps 10-minute video
Tools called
file_size_calculator
YouTube's recommended bitrate for 4K60
Tools called
bitrate_recommendation
Export settings for Vimeo
Tools called
platform_export_settings
What frame rate should I shoot sports at?
Tools called
frame_rate_guide
What does CRF mean?
Tools called
codecwise_glossary

About

Codecwise is a fully local video codec/container reference & compression calculator. codec_info explains one codec's compression efficiency, hardware support, licensing, typical use and pros/cons; list_codecs covers all four (H.264/AVC, H.265/HEVC, Apple ProRes, AV1). container_info explains one container's compatibility, streaming support and typical codecs; list_containers covers all five (MP4, MOV, MKV, WebM, AVI). file_size_calculator computes file size directly from bitrate and duration. bitrate_recommendation gives YouTube's own published recommended upload-bitrate range for a resolution, frame rate and SDR/HDR. platform_export_settings gives recommended container/codec/audio/bitrate settings for YouTube and Vimeo (from their own documentation) or short-form social platforms, or lists them all. frame_rate_guide explains which frame rate suits a stated content type or lists the full reference. codecwise_glossary defines core terms: codec, container, bitrate, CBR/VBR, keyframe/GOP, chroma subsampling, hardware encoding, lossy vs lossless, transcoding, CRF. Keyless; fully local; zero upstream calls; nothing stored.

Sources: Codec/container tradeoff explanations are original synthesis of well-established technical characteristics; bitrate and export tables are sourced directly from YouTube Help and Vimeo Help Center documentation, verified 2026-09-25; fully local, zero upstream calls

Privacy

The publisher, Unify Dynamics LLC, states that tool inputs are processed in memory and not retained.

Data not collectedNo account, no profile, no stored prompts or results.
Privacy policyTerms

What it can do

9 tools, grouped by job. Every one is read-only or compute-only.

OpenAPI
Codecs & Containers4 tools
  • Codec infoOne codec's compression efficiency, hardware support, licensing, typical use, and pros/cons.
  • List codecsEvery codec Codecwise covers: H.264/AVC, H.265/HEVC, Apple ProRes, AV1.
  • Container infoOne container format's compatibility, streaming support and typical codecs.
  • List containersEvery container format Codecwise covers: MP4, MOV, MKV, WebM, AVI.
Calculators2 tools
  • File size calculatorComputes file size directly from a bitrate and duration (bitrate x time), independent of any codec- specific lookup table.
  • Bitrate recommendationYouTube's own published recommended upload-bitrate range for a resolution, frame rate and SDR/HDR.
Export Guidance3 tools
  • Platform export settingsRecommended container/codec/audio/bitrate export settings for a named platform, or every platform if none given.
  • Frame rate guideWhich frame rate suits a stated content type, or the full reference if none given.
  • Codecwise glossaryDefinitions of core codec/compression terms: codec, container, bitrate, CBR/VBR, keyframe/GOP, chroma subsampling, hardware encoding, lossy vs…

Information

PublisherUnify Dynamics LLC
CategoryDesign & creative · Everyday life
LanguagesEnglish
Built forWorldwide
CompatibilityAny MCP client · any agent · REST
Version0.1.0
MCP endpointhttps://codecwise.connectorbay.com/mcp
REST APIopenapi.json
SupportGet help · Status
CountryWorldwide

More like this

Light Setup

Rembrandt, butterfly, split, loop — plus a computed lighting-ratio calculator

Live · MCP + REST10 tools

Video Hooks

Why short-video hooks and retention structures actually work, grounded in attention psychology

Live · MCP + REST9 tools

GIF Craft

GIF vs WebP vs APNG vs video, spec-verified, plus a computed size estimator

Live · MCP + REST10 tools

Post Sizes

Exact pixel sizes, aspect ratios and safe zones for every platform's post, story, reel and thumbnail

Live · MCP + REST9 tools

Shot Glossary

Shot types, camera movements, angles and composition — a hand-curated filmmaking glossary

Live · MCP + REST10 tools

Photo Composition

Rule of thirds, leading lines, symmetry — plus exact computed grid coordinates

Live · MCP + REST9 tools

Documentation

Back to top

What Codecwise is for

"What's the difference between H.264 and H.265?", "file size of a 50 Mbps 10-minute video?", "YouTube's recommended bitrate for 4K60?" — real codec/container tradeoffs and real math, not marketing copy.

What it does

codec_info explains one codec's compression efficiency, hardware support, licensing, typical use and pros/cons — H.264/AVC, H.265/HEVC, Apple ProRes, and AV1 (list_codecs covers all four). container_info explains one container format's compatibility, streaming support and typical codecs — MP4, MOV, MKV, WebM, AVI (list_containers covers all five). file_size_calculator computes file size directly from a bitrate and duration — straightforward arithmetic, independent of any codec-specific lookup table. bitrate_recommendation gives YouTube's own published recommended upload-bitrate range for a resolution, frame rate and SDR/HDR. platform_export_settings gives recommended container/codec/audio/bitrate settings for YouTube and Vimeo (from their own published documentation) or short-form social platforms, or lists every platform. frame_rate_guide explains which frame rate suits a stated content type — cinematic/film, vlog/broadcast, sports/action, slow motion — or gives the full reference. codecwise_glossary defines core terms: codec, container, bitrate, CBR/VBR, keyframe/GOP, chroma subsampling, hardware encoding, lossy vs lossless, transcoding, CRF.

What it is not

Not an encoder — it computes and explains, it doesn't transcode your actual file. Codec and container comparisons are original synthesis of well-established, stable technical characteristics. Bitrate and export tables are sourced directly from YouTube's and Vimeo's own published documentation as of the connector's build date; platforms occasionally revise these figures, so re-check the source before treating a number here as a hard delivery requirement.

Privacy policy

Back to top

Codecwise — Privacy Policy

Effective 25 September 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Codecwise is. Codecwise is a connector (an MCP server and REST API) that AI assistants and personal agents call on your behalf for a fully local video codec/container reference and compression calculator, combining original codec/container tradeoff explanations with bitrate and export tables sourced from platforms’ own published documentation. You interact with your assistant; the assistant sends us only the arguments needed for that one lookup or calculation.

What we receive. The arguments of each tool call — a codec name, a container name, a bitrate and duration, a resolution and frame rate, or a platform name — the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant, and a Pro API key if you have one), and standard server logs.

Everything is answered from bundled reference data and/or local computation, and nothing is stored. No request is forwarded to any third party — there is no upstream call at all, live or otherwise — and no query is logged in request bodies, recorded, or used to train anything.

What we do not receive or store. We do not receive your conversation with the assistant or your name, and we do not build a profile from your queries: each request is answered independently and nothing carries over between requests. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting-provider access logs, which contain IP addresses and request paths but not request bodies, are retained for up to 30 days for security and abuse prevention.

Sub-processors. None — the entire dataset is bundled with the server and answered locally. Hosting: Vercel (United States regions).

Legal bases and your rights. Our processing is necessary to provide the service you request through your assistant. Because we store no personal data beyond short-lived logs, requests to access, correct or delete personal data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. We do not sell or share personal information and do not use your data to train models.

Children. Codecwise is a general-audience service operated by the adult using the assistant.

Changes. We will post changes here with a new effective date.

Terms of service

Back to top

Codecwise — Terms of Service

Effective 25 September 2026. These terms govern use of the Codecwise connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

  1. The Service. Codecwise returns codec/container reference explanations, direct file-size calculations, and bitrate/export-setting tables sourced from platforms’ own published documentation (YouTube Help, Vimeo Help Center). It is accessed through an AI assistant or directly over MCP or HTTP.
  2. Reference tables, not a delivery guarantee. Codecwise’s bitrate and export-setting tables are sourced from platforms’ own published documentation as of the connector’s build date. Platforms occasionally revise these figures — always confirm against the current source before treating a number here as a hard delivery requirement.
  3. Reference, not real-time guidance. Content reflects general, widely published practice as of the build date stated in the Service's own data or responses. It does not know your specific situation, equipment, or context, and it cannot replace judgment formed through experience or professional consultation where relevant.
  4. Acceptable use. Automated use within the published rate limits is welcome.
  5. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time.
  6. Data. Our Privacy Policy describes what we process. In short: your request is answered from bundled reference data and/or local computation, and nothing is stored.
  7. Pro keys. Optional Pro API keys are issued at our discretion, are personal to the holder and may be revoked for abuse.
  8. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss, injury, or damage arising from use of, or reliance on, the Service. Our total liability is limited to US $100.
  9. Governing law. California law; venue in San Mateo County, California.
  10. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/codecwise

Support

Back to top

Video Codec Guide support

Email agent@connectorbay.com. We answer within two business days.

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Video Codec Guide never asks for them.

Get Video Codec Guide

Free · No sign-in · Read-only

Streamable HTTP, stateless, no authentication. Paste the endpoint into any MCP-capable agent.

https://codecwise.connectorbay.com/mcp
{
  "mcpServers": {
    "codecwise": {
      "type": "http",
      "url": "https://codecwise.connectorbay.com/mcp"
    }
  }
}