Introduction
The bug spec is for creating small graphics that sit in the corner of the big screen, typically during replays.
Submission & Deadlines
All content is submitted via our content management portal MKTG Drop.
Instructions for uploading and re-using content via MKTG Drop can be found here..
Digital content deadline
Print deadline
6 weeks before first display
6 weeks before first display
Contact MKTG immediately if you are unable to meet these deadlines.
Late content may not be able to be displayed.
General content guidelines
What works best
- High contrast graphics
- Bold logos and type
- Dark backgrounds with light text / logos
- Short messages
-
Have the main message on screen for
majority of the time
What to avoid
- Flashing or overly distracting graphics
- Very fast movement
- Small or thin text
- Limit unbranded time and space
When creating bugs it is important not cover too much of the big screen vision. We recommend taking up no more than 400 pixels wide and 200 pixels height.
Bugs should be in the lower left or lower right corner.
Bug spec
The bug spec is for creating small graphics that go over the big screen live vision, typically replays.
Dimensions
| Dimensions | Title safe |
|---|---|
|
1920x1080 |
60 pixels |
File format
| Content | File type | Codec |
|---|---|---|
|
Static |
.png |
RGB with alpha |
MKTG Drop asset
| MKTG Drop Asset |
|---|
|
Big Screen - Elements |
All content is submitted via our content management portal MKTG Drop.
Instructions for uploading and re-using content via MKTG Drop can be found here..
Examples
