> For the complete documentation index, see [llms.txt](https://guides.advertising.webtoon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.advertising.webtoon.com/creative-guidelines/with-creator-ads/branded-epilogue-story-bep.md).

# Branded Epilogue Story (BEP)

### Placement and Features

* This ad is a collaboration between a WEBTOON title and a brand, to be displayed in **short epilogue format** at the end of the main episode for the select title.
* There will be a banner located at the bottom of the viewer that brings users to the external ad link.
* High user participation is anticipated given the familiar characters and plot for existing readers.

<figure><img src="/files/0Vhju3n3vFUdDcvj0yKG" alt="" width="563"><figcaption><p>Branded Epilogue Story(BEP), Viewer-end Ad</p></figcaption></figure>

### Required Assets

* Submit in PSD and JPG format, as creator must design the assets

<div><figure><img src="/files/amoyh03E7P1s64l03GgR" alt="" width="375"><figcaption><p>Branded Epilogue Story(BEP)</p></figcaption></figure> <figure><img src="/files/Ic5oIxqYYG6wgaQP0nlz" alt="" width="225"><figcaption><p>Viewer-end Ad</p></figcaption></figure></div>

<table><thead><tr><th width="108.952392578125">Asset</th><th>Dimensions</th><th width="105.857177734375">Resolution</th><th>File Format</th><th>File Size</th><th>Required Asset</th></tr></thead><tbody><tr><td>Branded Epilogue Story(BEP)</td><td>800x5000px</td><td>300 dpi</td><td>PSD, Clip Studio</td><td>-</td><td>4-5 panels</td></tr><tr><td>Branded Epilogue Story(BEP)_Slice</td><td>800x1280px</td><td>300 dpi</td><td>JPG</td><td>Up to 150MB per page</td><td>-</td></tr><tr><td>Viewer-end Ad</td><td>600x600px</td><td>-</td><td><p>PSD</p><p>JPG, PNG</p></td><td>Up to 150KB</td><td>Main ad creative and ad copy</td></tr></tbody></table>

## Branded Epilogue Story(BEP) Design Guide

**Branded Epilogue Story(BEP) Manuscript**

* Width: 800px
* Maximum Height: 5000px
* 4-5 panels
* **Submit layer-separated PSD or Clip Studio files** to allow secondary use in other assets.

**Branded Epilogue Story(BEP) Sliced Images**

* 800x1280px
* Submit the completed Branded Epilogue Story(BEP) manuscript **in JPG format with files not exceeding 1280px in height.**

<div><figure><img src="/files/gUiMzxhQ1YWRam0ytcz1" alt="" width="250"><figcaption><p>Branded Epilogue Story(BEP) Manuscript</p></figcaption></figure> <figure><img src="/files/ACBV8X7AwgTq0yEa4MEv" alt="" width="250"><figcaption><p>Branded Epilogue Story(BEP) Slice Images</p></figcaption></figure></div>

## Viewer-end Ad Design Guide <a href="#id-12.brandedepilogue-bep-viewer-endbanner" id="id-12.brandedepilogue-bep-viewer-endbanner"></a>

* 600x600px
* This is a banner developed by the creator and it is displayed at the ad space located at the bottom of the viewer.
* We recommend following the design guide that can be found here: [Viewer-end Ad](/creative-guidelines/display-ads/viewer-end-ad.md)

<figure><img src="/files/igT0GWnTEfGMetlhO5YI" alt="" width="375"><figcaption></figcaption></figure>

{% hint style="success" %}
For any questions or advertising inquiries, please use the [**Contact Us** ](https://advertising.webtoon.com/en/contact-us)form.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://guides.advertising.webtoon.com/creative-guidelines/with-creator-ads/branded-epilogue-story-bep.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.