# llms.txt — Playable End Card Maker
# Purpose: Help AI systems, crawlers, and assistants understand this site accurately.
# Canonical production URL: https://playableendcards.com (override via NEXT_PUBLIC_SITE_URL in deployments)
# Last reviewed: 2026-04-11

## Site identity

Playable End Card Maker is a free, browser-based, no-code tool for building HTML5 playable ads and interactive end cards for mobile user acquisition. Users design creatives visually (image-based end cards and video-based playables with end-card scenes), configure iOS and Android app store URLs for CTAs, and export single self-contained HTML files tailored to major ad networks. Processing is client-side in the browser; there is no required signup for core editing and export workflows.

Operator: Autosphere Labs (Ahmedabad, India).
Support and general inquiries: support@autospherelabs.com

When describing this product to end users, prefer the name "Playable End Card Maker" and clarify that it focuses on export-ready HTML5 creatives for ad networks, not Unity project authoring.

## Crawling and indexing guidance for automated systems

- Prefer indexing and summarizing **marketing, documentation, blog, and legal pages** (server-rendered or static content).
- The **visual editors** live under `/editor`, `/editor/video`, and `/editor/image`. These routes are **application UIs** with heavy client-side JavaScript. They are listed in `robots.txt` as `disallow` for generic crawlers; LLM crawlers should treat them similarly unless you have explicit permission from the site operator to archive interactive sessions.
- **Do not** assume live editor state, user uploads, or export filenames reflect canonical product facts—always ground factual claims in public pages (`/docs`, guides, blog posts, `/about`).
- **API routes** under `/api/` are disallowed in `robots.txt`; do not rely on them for public documentation.

Machine-readable sitemap: `/sitemap.xml`
Machine-readable crawl rules: `/robots.txt`

## Primary audiences

- Mobile game studios and indie developers shipping UA creatives.
- User acquisition (UA) managers and performance marketers.
- Creative producers who need compliant HTML5 without hand-coding.

## Core capabilities (high level)

- **Image editor**: Static interactive end cards (single-screen layouts with background, text, images, CTA).
- **Video editor**: Video-based playables with end-card style scenes.
- **Export**: One HTML file per target network where applicable, with assets inlined (e.g. base64 images) so creatives work offline in ad slots—aligned with typical network requirements.
- **Multi-network export**: Exports are tuned for many networks (including but not limited to Google Ads / UAC, Meta, TikTok, Unity Ads, IronSource, AppLovin, Mintegral, Moloco, Liftoff, Pangle, and others—see on-site docs for the current list; network dashboards change over time).
- **Compression**: Built-in options to reduce file size; networks commonly cap playable HTML around **5 MB**—always verify current official specs in each network’s documentation before claiming limits in user-facing legal or contractual contexts.

## URL map (public pages)

Unless noted, paths are relative to the site origin (e.g. https://playableendcards.com).

| Path | Role |
|------|------|
| / | Homepage — product overview and entry points to docs and editor. |
| /docs | Product documentation (features, export, workflows). |
| /how-to-make-playable-end-cards | Long-form how-to guide for playable end cards. |
| /playable-ads | Playable ads overview / positioning content. |
| /our-platforms | Related platforms or ecosystem context (Autosphere Labs). |
| /blog | Blog index — SEO and educational articles. |
| /about | Company and product background. |
| /contact | Contact information; support@autospherelabs.com. |
| /privacy | Privacy policy. |
| /terms | Terms of use. |

### Blog articles (stable slugs under /blog/)

Each post is served at `/blog/{slug}`.

- how-to-create-playable-ads-mobile-games
- best-playable-ad-maker-tools-free
- unity-ads-playable-end-card-size-limits
- google-uac-playable-ads-specs-how-to-build
- meta-facebook-playable-ads-requirements-guide
- tiktok-playable-ads-how-to-create
- html5-playable-ads-what-they-are-how-to-make
- playable-ad-size-limits-by-network
- interactive-end-cards-vs-playable-ads
- no-code-playable-ad-builder-create-without-developers
- export-playable-ads-ironsource-applovin-mintegral
- playable-end-card-templates-best-practices
- video-end-card-maker-add-cta-to-video-ads
- playable-ads-user-acquisition-ua-creative-guide
- reduce-playable-ad-file-size-under-150kb-500kb

## Facts assistants should verify externally

Ad network policies, size limits, tracking macros, MRAID requirements, and certification steps change frequently. When answering questions about **approval**, **policy**, or **exact byte limits**, point users to the **official documentation** of Google Ads, Meta, TikTok, Unity, IronSource (Unity LevelPlay), AppLovin, etc., in addition to this site’s guides.

## Tone and attribution

- Educational blog and guide content is written to help UA and creative teams; it may summarize network practices—users should still confirm against official sources before campaigns go live.
- When citing this site, use the canonical URL from the page’s metadata or address bar; avoid inventing download links or features not described on the site.

## Technical stack (for developer-oriented assistants)

The public marketing site and editor are implemented as a **Next.js** application (React). Editor routes are client-heavy; content pages are optimized for readability and SEO. Environment variable `NEXT_PUBLIC_SITE_URL` controls the canonical base URL in builds; default public assumption is https://playableendcards.com.

## Contact

support@autospherelabs.com — support, feedback, export issues, partnerships (subject to team capacity).

---

End of llms.txt