ForHosting KIT · Web Scraping & Monitoring

Twitter Card meta tag generator

Type a title such as Build & Ship and get Twitter Card tags ready to paste into your page's head, the ampersand safely written as &. Pick the compact summary card or the large-image one; empty optional tags are left out. Free in your browser.

Free
Runs in your browser
No sign-up
Your data stays on your device

Run — free How it works & API

Use it from WebAPIEmailTelegramApp soon

Create a complete Twitter Card meta tag set without memorizing property names or worrying about unsafe characters in HTML attributes. Choose a supported card type, add the preview title, and optionally include a description and absolute image URL. The generator returns both structured tag records and a ready-to-paste HTML block. It runs deterministically with no network requests, so the same input always produces the same markup and your page data is not sent to a third-party preview service.

Choose the card format that matches the preview

Start with the visual treatment you want when a link is shared. The summary card is the compact option: it is appropriate for articles, documentation, product pages, and other links where the title and description should remain dominant while an image acts as a supporting thumbnail. Other Twitter Card types require additional fields that are not part of this contract.

If you submit an unsupported type, the capability returns a typed input error instead of silently producing incomplete markup. That behavior makes automation safer: a spelling mistake or incompatible type cannot pass through as a tag set that looks plausible but fails to represent the intended card.

Supply content that survives HTML safely

The title is required and must contain non-whitespace text. A description and image are optional, so their tags are omitted when you do not supply them; the output never fills missing fields with empty tags or null values. Relative paths may work inside your own site, but social crawlers need an address they can request independently, which is why this generator rejects them.

Text is escaped for use inside a double-quoted HTML attribute. Ampersands, quotation marks, angle brackets, and apostrophes are converted to their corresponding character references, preserving the visible wording without allowing the content to break the tag boundary. The returned structured records retain the normalized human-readable values, while the HTML block contains the escaped representation intended for markup.

This distinction is useful when an application wants to inspect or store the metadata separately from the snippet it inserts into a document head.

Install and verify the generated tags

Copy the returned HTML lines into the head element of the page that will be shared. Keep one tag for twitter:card and one for twitter:title, followed by twitter:description and twitter:image when those optional values are present. After deployment, inspect the page source from a public URL to confirm that the server actually emits the tags in the initial HTML.

Client-side code that adds metadata only after loading may be invisible to crawlers, and a protected or private image cannot be fetched even when its URL is syntactically valid. The generator validates the metadata you provide, but it does not contact your site, download the image, measure image dimensions, or predict how any social platform will crop a preview. Cache behavior also belongs to the platform that fetches the page, so an older preview may remain visible after you update the tags.

What you can do with it

Add social tags in a static-site build

Generate predictable structured records and HTML for each page without calling a network service or maintaining a tag template.

Catch unsupported card selections

Reject incompatible or misspelled card types before incomplete metadata reaches a production page.

FAQ

Is an image required?

No. When image is omitted, the result omits the twitter:image tag.

What happens when the description is omitted?

The twitter:description tag is omitted entirely. The output does not create an empty tag or a null field.

Does the generator escape quotation marks and ampersands?

Yes. Characters that could break an HTML attribute are encoded in the HTML output while the structured tag records retain their readable values.

Does this check how the live card will look?

No. It generates and validates the supplied metadata locally; it does not fetch the page, inspect the image, or contact a social preview service.

Which card type should I choose?

Choose summary when the title and description should lead and the image is only a thumbnail, as with articles, documentation or product pages. Choose the large-image summary when the artwork carries meaning, as with editorial features, launches, portfolios or recipes.

Why is my image address rejected?

The image needs a full web address beginning with http:// or https://. A relative path such as /images/social-card.jpg may work inside your own site, but social crawlers need an address they can fetch on their own.

Related tools

For developers — API access

Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.

API endpoint

POSThttps://api.kit.forhosting.com/web/twitter-card-generate

Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.

Call it from your stack

curl -X POST https://api.kit.forhosting.com/web/twitter-card-generate \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"card_type":"summary_large_image","title":"A Practical Guide to Accessible Forms"}'

const res = await fetch("https://api.kit.forhosting.com/web/twitter-card-generate", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.KIT_KEY}`,
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    "card_type": "summary_large_image",
    "title": "A Practical Guide to Accessible Forms"
  })
});
const { task_id } = await res.json();

import os, requests

res = requests.post(
    "https://api.kit.forhosting.com/web/twitter-card-generate",
    headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
    json={
    "card_type": "summary_large_image",
    "title": "A Practical Guide to Accessible Forms"
},
)
task_id = res.json()["task_id"]

<?php
$res = file_get_contents("https://api.kit.forhosting.com/web/twitter-card-generate", false, stream_context_create([
  "http" => [
    "method"  => "POST",
    "header"  => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
    "content" => '{"card_type":"summary_large_image","title":"A Practical Guide to Accessible Forms"}',
  ],
]));
$task = json_decode($res, true);

body := bytes.NewBufferString(`{"card_type":"summary_large_image","title":"A Practical Guide to Accessible Forms"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/web/twitter-card-generate", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)

Example request

{
  "card_type": "summary_large_image",
  "title": "A Practical Guide to Accessible Forms"
}

Example response

{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "web.twitter_card_generate",
  "status": "queued",
  "_links": {
    "result": "/tasks/tsk_…/result"
  }
}

The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.

Pricing

Per request$0.002

Published price — no tokens, no invented credits. A failed task is never charged.

Limits

`timeout_sec`	30
`max_crawl_pages`	25

Errors

HTTP	Code	Meaning
`401`	`unauthorized`	Missing or invalid API key.
`402`	`insufficient_balance`	Your balance doesn't cover the task price.
`404`	`unknown_type`	That task type doesn't exist.
`429`	`rate_limited`	Too many requests. Use the webhook instead of polling.

Technical notes

Choose the card format that matches the preview

The summary_large_image card gives the image much more visual weight and works well for editorial features, launches, portfolios, recipes, and pages whose artwork carries useful context. This generator deliberately supports those two general-purpose formats because they can be described completely by a card type, title, description, and image.

Supply content that survives HTML safely

When an image is present, it must be an absolute HTTP or HTTPS URL.

Install and verify the generated tags

For automated publishing, the API costs $0.002 per request; the browser version uses the same deterministic logic.

Integration use cases

Prepare metadata for a new article

Turn an article headline, synopsis, and hero image URL into a paste-ready summary_large_image tag block.

Technical questions

Which Twitter Card types are supported?

The generator supports summary and summary_large_image. It returns an invalid_input error for any other card type.

What does API generation cost?

Each API request costs $0.002. The browser version runs locally using the same deterministic algorithm.

Read the full KIT documentation →

Run — free

Choose the card format that matches the preview

Supply content that survives HTML safely

Install and verify the generated tags

What you can do with it

Add social tags in a static-site build

Catch unsupported card selections

FAQ

Related tools

For developers — API access

API endpoint

Call it from your stack

Example request

Example response

Pricing

Limits

Errors

Technical notes

Choose the card format that matches the preview

Supply content that survives HTML safely

Install and verify the generated tags

Integration use cases

Prepare metadata for a new article

Technical questions

thank you