Roblox creator media kit: channel evidence, formats and clear terms

Make the first screen answer three questions

Explain what you create, which audience you serve and what a developer can reasonably ask you to produce. “Roblox creator making first-session explanations for cooperative games” tells a partner more than “gaming influencer.” Put one preferred business contact beside the summary and link to relevant channels. Use a contact you intend to make public; do not expose a personal address just to fill a field.

A media kit is a decision aid, not a wall of every achievement. A developer should be able to check your style, relevant audience and available format quickly. Keep a working date on the kit and change it when the offer or evidence changes. You can hold the detailed report privately and share a short public summary without publishing personal audience data.

Present channel evidence without inflating reach

Give each channel its own platform, language, format and observation window. Choose a recent consistent sample, explain how many posts it contains and separate sponsored content from organic work. Report a median or range if one unusually large post would distort the average. Say whether figures come from your own platform dashboard, public observations or a manual estimate.

Never add followers across platforms and call the sum unique reach. Views, subscribers and live peak viewers are different measures. If audience geography or age data is unavailable, leave it unknown. Crop evidence to the agreed fields and remove private names, messages and account details before sharing. A dated screenshot helps a developer check context; it does not make future delivery predictable.

Choose examples that prove the format

Select two or three examples near the work you want next. For each one, give the public URL, your role, deliverable, publication date and one sentence on the creative choice. A good example might show how you explained a mechanic, handled an honest first attempt or brought a community into an event. Get permission before naming a private partner or publishing a confidential brief.

Label an unpaid sample as a self-initiated example. If it uses fictional game details, mark it illustrative. If a sponsor approved content reuse only on your channel, do not place their raw assets in a downloadable kit. Where results can be shared, state their source and period and distinguish your contribution from the game team’s work. Content views alone do not demonstrate player acquisition or game revenue.

A worked one-page kit

The creator “Co-op Lens” below is fictional. The example deliberately uses fields and scope rather than impressive invented follower counts. Replace placeholders with your own supported evidence. A small channel with a clear format can be assessed more fairly than a large unexplained headline number.

Keep the public version short enough to scan. Use links for portfolio examples and a separate dated channel report when requested. If you offer different languages or formats, state which version is included in the quote; translation, subtitles and another platform can add production work.

Quote production and rights separately

Start with the deliverable you can control: a finished video, a defined live session or a community event with a planned duration. Quote the base production and publication scope, then list optional rights or extra work. You do not need to publish one universal rate if projects differ, but explain which information you need to produce a useful quote.

Ask the developer for the game URL, playable access, goal, format, deadline, factual review needs and intended reuse. Paid advertising, an edited version on the developer’s channel, source files and category exclusivity are separate rights questions. Agree their duration and platforms rather than granting “all rights forever” by accident. Spell out cancellation, late access, revision limits and the report you can actually supply.

Protect a truthful creative and reporting process

Agree a factual review window and the number of correction rounds before recording. You can correct a wrong game name or unsupported device claim without promising a positive review. Include the planned disclosure in the scope. YouTube requires creators to declare paid promotions to the platform; other applicable disclosure duties also need to be addressed.

Ask the developer for the final link and test it before publication. If they supply a Roblox Share Link, preserve it and agree placement. Your platform views remain separate from game players. Do not promise player attribution from a UTM parameter or a link-click total.

1. Confirm access, honest-review boundaries, disclosure and usage rights in writing.
2. Publish the agreed material and save its URL and timestamp.
3. Report the agreed fields with source, period and any unavailable data.
4. Ask permission before adding the collaboration and its results to your public portfolio.

Turn the kit into a MARPLA profile

Bring your channels, format descriptions, portfolio and selected public business contacts into one profile. An existing MARPLA member uses the same account for creator and developer roles. Prepare the profile as a draft, review what will be visible and explicitly publish when ready. Open the creator overview for a concise shareable introduction.

MARPLA’s network is still growing. Publishing a profile does not guarantee enquiries, paid orders or income. Built-in payments, held funds and escrow protection are unavailable; paid fulfilment inside the platform is blocked until payments are connected. Check the product guide for the supported free and barter workflow. Keep your quoted commercial terms and your expected performance clearly separate.

Primary sources

• YouTube Help — Paid promotion disclosure
• Roblox Creator Hub — Share Links