Are Discord snowflake IDs typed as strings or numbers?

Strings. Discord returns snowflakes as JSON strings because they exceed Number.MAX_SAFE_INTEGER. The converter preserves that — string typing avoids precision loss.

Does it cover embeds, attachments, and components?

Yes. Paste a message with embeds, attachments, or message components and each becomes a typed nested interface, with arrays merged across variants.

Webhook execute response or bot message?

Both work. POST /webhooks/{id}/{token}?wait=true returns a Message object with the same shape as the bot Message endpoints, so one paste gives you types reusable across both.

Discord Webhook Message to TypeScript — Message object → TS interface

JSON input valid

TypeScript output

About this conversion

Discord's Message object carries author, content, embeds, attachments, mention arrays, components, and a tangle of timestamps and snowflake IDs. All snowflakes are returned as strings (never numbers) because they exceed Number.MAX_SAFE_INTEGER — getting that detail right by hand is a common source of bugs. Pasting a real response from a webhook with wait=true produces a TypeScript interface that matches exactly what Discord sent, snowflakes-as-strings included.

The official discord-api-types package covers everything but pulls in a large surface when you only need the message shape for one webhook. Generated types from a live payload are tighter, easier to inline into a Cloudflare Worker or Vercel function, and stable across discord-api-types version bumps. Paste a message that includes embeds, components, or interaction_metadata and the converter merges the variation into one accurate interface.

Discord Webhook Message to TypeScript

About this conversion

Same shape, other validators

Other JSON shapes