ブロックチェーン広告ヘルプセンター

広告クリエイティブのアップロード方法:形式と仕様

White curved contour lines forming an abstract shape on a black background.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
ヘルプセンター
広告クリエイティブのアップロード方法:形式と仕様
トピックス

Uploading your ad creatives or assets is an essential step to launching a new campaign. Follow these specs to ensure compatibility and approval.

Specs to Upload Ad Assets

フォーマット ファイル形式 最大サイズ 推奨サイズ 追加仕様 主な掲載場所
ディスプレイ JPG, PNG, GIF 700KB 300×250, 728×90, 320×100, 300×600, 160×600, 970×90, 320×50, 468×60 アニメーション:最大30秒、3ループ サイドバー、ヘッダー、フィード内
ネイティブ JPG, PNG(画像) 700KB 1200×628(1.91:1)または 600×600(最小 600×314) 見出し:20文字;説明:50文字;
CTA:15文字
メディア:1200x628
フィード、記事
動画 MP4, MOV, AVI(H.264 推奨) 700 KB 16:9(横)または 9:16(縦) 15〜30秒、30fps、AAC/MP3 128kbps以上;プログレッシブスキャン;固定フレームレート フルスクリーン、ページ内
アプリ内 JPG, PNG(バナー/ネイティブ) 700KB バナー:320×50, 320×100, 320×480;ネイティブ:上記と同様 タッチ対応、モバイル最適化 モバイルアプリ、インタースティシャル
プッシュ通知 JPG, PNG(アイコン + 画像) アイコン:500KB / 画像:2MB アイコン:192×192;画像:300×250, 320×100, 728×90, 320×50 タイトル:30文字;説明:40文字;CTA:20文字 デバイス/ブラウザ通知
ポップ(ポップアップ & ポップアンダー) JPG, PNG, GIF 2MB 300×250, 320×100, 728×90, 320×50 パブリッシャーサイトからの新しいタブ/ウィンドウ
HTML5 広告 ZIP(HTML/CSS/JS) 2 MB 300×250, 300×600, 728×90, 160×600, 320×50, 320×100 インラインまたはバンドルされたJSのみ(外部JSライブラリ不可);すべてのアセットはHTTPS経由で読み込む;ユーザー操作なしでレンダリング;重いアニメーションは避ける ディスプレイ掲載面
Performance Max JPG, PNG, GIF, MP4, MOV, AVI アセットごとに700KB フォーマットにより異なる(ディスプレイ + ネイティブ + 動画の組み合わせ) すべてのフォーマットで自動的に最適化された組み合わせを配信 クロスフォーマット掲載面
Flux – ディスプレイ JPG, PNG, GIF 700KB 300×250, 728×90, 320×100, 300×600, 160×600, 970×90, 320×50, 468×60 インプレッションごとにAI生成クリエイティブ;ディスプレイと同じ仕様 サイドバー、ヘッダー、フィード内
Flux – ネイティブ JPG, PNG(画像) 700KB 1200×628(1.91:1)または 600×600(最小 600×314) 見出し:60文字;説明:150文字;ロゴ:128×128;インプレッションごとにAI生成 フィード、記事

Uploading your ad creatives or assets is an essential step to launching a new campaign. Follow these specs to ensure compatibility and approval.

Specs to Upload Ad Assets

Format File Types Max Size Recommended Dimensions Additional Specs Common Placement
Display JPG, PNG, GIF 700KB 300×250, 728×90, 320×100, 300×600, 160×600, 970×90, 320×50, 468×60 Animation: 30 sec max, 3 loops Sidebars, headers, in-feed
Native JPG, PNG (image) 700KB 1200×628 (1.91:1) or 600×600 (min 600×314) Headline: 20 chars; Description: 50 chars; CTA: 15 chars; Media: 1200x628 Feeds, articles
Video MP4, MOV, AVI (H.264 preferred) 700 KB 16:9 (horizontal) or 9:16 (vertical) 15–30 sec, 30 fps, AAC/MP3 128 kbps+; progressive scan; fixed frame rate Full-screen, in-page
In-App JPG, PNG (banner/native) 700KB Banners: 320×50, 320×100, 320×480; Native: same as above Touch-friendly, mobile-optimized Mobile apps, interstitials
Push Notification JPG, PNG (icon + image) Icon: 500KB / Image: 2MB Icon: 192×192; Image: 300×250, 320×100, 728×90, 320×50 Title: 30 chars; Description: 40 chars; CTA: 20 chars Device/browser notifications
Pop (Pop-ups & Popunders) JPG, PNG, GIF 2MB 300×250, 320×100, 728×90, 320×50 New tab/window from publisher site
HTML5 Ads ZIP (HTML/CSS/JS) 2 MB 300×250, 300×600, 728×90, 160×600, 320×50, 320×100 Inline or bundled JS only (no external JS libraries); all assets must load over HTTPS; render without user interaction; avoid heavy animations Display placements
Interstitials JPG, PNG (static); HTML5 (rich media) 700KB (static); 2MB (HTML5) Full-screen responsive Close button required after configurable delay; static or HTML5 rich media accepted Between page loads, app screens, or game levels
Performance Max JPG, PNG, GIF, MP4, MOV, AVI 700KB per asset Varies by format (Display + Native + Video combined) Runs optimized mix across all formats automatically Cross-format placements
Flux – Display JPG, PNG, GIF 700KB 300×250, 728×90, 320×100, 300×600, 160×600, 970×90, 320×50, 468×60 AI-generated creative per impression; same specs as Display Sidebars, headers, in-feed
Flux – Native JPG, PNG (image) 700KB 1200×628 (1.91:1) or 600×600 (min 600×314) Headline: 60 chars; Description: 150 chars; Logo: 128×128; AI-generated per impression Feeds, articles

Format-specific guidance

Use these notes as practical guidance; all hard requirements (file types, sizes, dimensions, character limits) are in the table.

  • Display (Banners): Use clean, responsive-friendly designs that work across multiple sizes and devices. Avoid overly aggressive animation, flashing, or cluttered layouts to reduce banner blindness and potential policy issues.
  • Native: Use high-resolution images (at least 72 dpi) with clear focal points, and avoid cropping more than roughly 20% of the subject to prevent awkward cuts in different placements. Align your headline, description, and CTA so the story is clear even if text truncates slightly.
  • Video: Use H.264 compression where possible for broad compatibility and fast load times. Design for sound-off environments (captions, strong visuals) and do not rely on auto-play, as not all publishers or users allow it.
  • In-App: Design mobile-first with large, tap-friendly CTAs and legible typography on small screens. Test both portrait and landscape orientations to ensure key elements are visible on common device sizes.
  • Push Notification: Keep copy extremely concise and action-oriented so it fits within device/browser notification UI without awkward truncation. Use simple, recognizable icons and lightweight images to ensure fast delivery even on slow networks.
  • Pop (Pop-ups & Popunders): Keep landing pages lean and fast: compress images, minimize scripts, and prioritize above-the-fold clarity on your primary value proposition and CTA. Ensure layouts gracefully adapt to common desktop and mobile resolutions.
  • HTML5 Ads: Keep animations smooth and lightweight, and avoid external JS libraries that could slow rendering or break in secure environments. Ensure the creative renders without user interaction and respects publisher UX (no auto-playing sound on load).
  • Interstitials: Use full-screen creatives designed for natural transition points, such as page loads, app screen changes, or game level breaks. Always include a clear close path after the required delay, and avoid forced, no-exit experiences that can harm user experience and publisher relationships.
  • Performance Max: Prepare a complete asset kit (display, native, and video) so the system can fully optimize delivery. Maintain visual and messaging consistency across all asset types to reinforce brand recognition.
  • Flux (Display & Native): Provide strong “source” assets (images, copy, and brand elements) so AI-generated variants remain on-brand. Periodically review performance and creative variants to ensure they align with your guidelines.

General Creative Policies

To protect users and support compliance (especially for finance, blockchain, and other regulated industries), all creatives must follow these rules:

  • No misleading, exaggerated, or unverifiable claims
  • No excessive flashing or strobing (max ~3 flashes per second)
  • Landing page must load in under 3 seconds on a standard connection
  • Ads and landing pages must respect GEO-specific regulations and disclosures
  • Content must be appropriate for brand-safe inventory and aligned with the advertised product

Advertisers running campaigns in regulated verticals should also ensure legal disclaimers and required risk warnings are clearly visible on the landing page (and, where relevant, within the ad).

Best practices: Match formats to objectives: e.g., video for storytelling, native for engagement, push for urgency. Compress images and videos (e.g., TinyPNG, HandBrake) to stay within size limits without losing clarity. Use clear CTAs (e.g., “Sign Up,” “Play Now,” “Learn More”) and keep key text within character limits to avoid truncation. Test creatives in HUB preview across desktop and mobile before submitting. Use high-resolution assets (72 dpi+), simple layouts, and legible font sizes to improve approval and performance.

Troubleshooting: Upload error: Confirm file type, max size, and dimensions match the table for your format. Preview not loading: Try a hard refresh, clear cache, or switch browsers. Disapproved creative: Re-check specs (dimensions, file size, text limits) and platform policies, then edit and resubmit. Unexpected cropping (native/push): Use the recommended aspect ratios and avoid placing critical content at the edges. Slow loading (video/HTML5/pops): Re-compress assets, reduce animation complexity, and audit third-party scripts.

Did this answer your question?
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
empty state image
No result found
Try adjusting your search to find what you're looking for.

今すぐ始めましょう

今すぐ登録してアフィリエイトになりましょう

Request Access