Writing an Emote Design Brief: Getting What You Want from Commissions

The emote you envision in your mind and the emote the artist creates are only as similar as your communication is clear. Vague briefs produce guessing; comprehensive briefs produce precision. Learning to write effective design briefs transforms commission experiences from frustrating interpretation gaps into collaborative creative success.

A design brief isn't bureaucracy—it's a communication tool that protects both parties. Artists want to satisfy clients but can't read minds. Clients want specific visions realized but often struggle to articulate them. Good briefs bridge this gap.

Why Design Briefs Matter

Understanding the value drives better briefs.

For You (The Client):

  • Clarifies your own thinking
  • Creates reference for evaluation
  • Reduces revision cycles
  • Ensures needs addressed
  • Protects expectations

For Artists:

  • Clear direction to work from
  • Reduced guessing and assumptions
  • Foundation for questions
  • Scope understanding
  • Fewer misunderstandings

For the Project:

  • Faster completion
  • Better results
  • Fewer revisions
  • Happier outcome for all
  • Professional process

Essential Brief Components

What every emote brief needs.

Project Overview:

Start with basics:

  • What type of asset (emote, badge, etc.)
  • How many emotes
  • Platform(s) intended
  • Timeline needs
  • Budget range

Character Information:

If character-based:

  • Reference images (existing art, descriptions)
  • Character name and personality
  • Key visual features
  • Color palette
  • Style direction

Expression/Emotion List:

For each emote:

  • Specific emotion or concept
  • Context for when it's used
  • Reference images if helpful
  • Any specific elements needed
  • Priority indicators

Technical Requirements:

Specify:

  • Size specifications (Twitch: 28/56/112)
  • File formats needed
  • Background requirements
  • Animation if applicable
  • Source file needs

Writing Clear Character Descriptions

Communicate character design effectively.

Physical Descriptions:

Be specific:

  • Face shape and features
  • Hair style and color
  • Skin tone
  • Body type (if relevant for emotes)
  • Distinguishing features

Visual References:

Images speak clearly:

  • Existing character art
  • Photos for inspiration
  • Other artists' work showing style direction
  • Color palette references
  • "Like this but..." examples

Personality Context:

Help artist capture character:

  • Core personality traits
  • How emotions typically show
  • Energy level
  • Any quirks that affect expressions
  • What makes this character distinct

Example Character Description:

"Character is a cat-eared streamer mascot. Female presenting, warm brown skin, bright purple hair in a messy bun with cat ears matching hair color. Big expressive eyes (anime style), small pointed nose, tends to smile widely. Energetic personality that shows through exaggerated expressions. Signature feature: galaxy-pattern cat ears that should be visible in all emotes."

Describing Expressions Effectively

Get the specific emotions you need.

Emotion Naming:

Be specific:

  • "Happy" is vague
  • "Laughing uncontrollably at chat" is specific
  • "Sad" is vague
  • "Wistfully disappointed but accepting" is specific

Context Description:

When would this emote be used?

  • "When chat makes a bad pun"
  • "When something hype happens"
  • "When I'm about to do something chaotic"
  • "When viewers donate"

Visual Elements:

Specific features to include:

  • Tears (of joy or sadness)
  • Blushing
  • Sparkle eyes
  • Sweat drop
  • Motion lines

Reference Images:

Show what you mean:

  • Screenshots of similar expressions
  • Emoji for quick reference
  • Other emotes that capture the feeling
  • Reaction images

Example Expression Brief:

"Expression 3: 'Pog' excitement

  • Emotion: Explosive excitement and hype
  • Use case: When something amazing happens on stream
  • Visual elements: Wide open mouth, sparkle/star eyes, possibly motion lines suggesting movement backward in shock
  • Reference: Similar energy to PogChamp but with our character
  • Notes: Should feel energetic enough to spam in chat moments"

Style Communication

Helping artists understand visual style.

Style References:

Show examples:

  • Artists whose work you admire
  • Existing emotes you like
  • Specific pieces that capture the vibe
  • Style comparison ("more chibi than realistic")

Style Specifics:

Define preferences:

  • Line work (thick/thin, colored/black)
  • Shading approach (flat, cel-shaded, soft)
  • Color saturation level
  • Detail level
  • Overall aesthetic

What to Avoid:

Note anti-references:

  • Styles you don't want
  • Specific elements to avoid
  • Common approaches you've seen that miss the mark
  • Deal-breakers

Technical Specification Section

Platform requirements matter.

Size Requirements:

For Twitch emotes:

  • 28x28 pixels (required)
  • 56x56 pixels (required)
  • 112x112 pixels (required)
  • Working resolution recommendation

File Format Needs:

Specify:

  • PNG for final exports
  • Transparency required
  • Source files (.psd, etc.) if wanted
  • Animation formats if applicable

Platform Specifics:

Mention platform needs:

  • Twitch requirements
  • Discord sizing
  • Additional platforms
  • Cross-platform considerations

Use EmoteShowcase's tools to verify emotes meet all technical specifications before final approval.

Providing Visual References

Images communicate better than words.

Types of References:

  • Character reference sheets
  • Color palette samples
  • Expression references
  • Style examples
  • Environment/context images

Reference Organization:

Make references usable:

  • Label each reference
  • Explain what's relevant in each
  • Note "like this" vs "not like this"
  • Don't overwhelm with too many

Creating a Reference Board:

Consider assembling:

  • Pinterest board
  • Google Drive folder
  • Single reference document
  • Clear organization system

Setting Expectations and Boundaries

Prevent misunderstandings upfront.

Revision Expectations:

Clarify:

  • How many revisions expected
  • What constitutes a revision vs. new work
  • Revision process
  • Final approval process

Communication Preferences:

State:

  • How to contact you
  • Response time expectations
  • Preferred update frequency
  • Decision-making process

Dealbreakers:

Note non-negotiables:

  • Elements that must be included
  • Approaches that won't work
  • Technical requirements that are firm
  • Aesthetic boundaries

Flexibility Indicators:

Where you're open:

  • "Open to artist interpretation on..."
  • "Flexible on exact pose..."
  • "Trust your judgment on..."
  • "Would love your input on..."

Brief Format and Organization

Structure for clarity.

Recommended Format:

Section 1: Project Overview

  • Number of emotes, budget, timeline

Section 2: Character Information

  • Description, references, key features

Section 3: Individual Emote Briefs

  • One section per emote with specifics

Section 4: Technical Requirements

  • Sizes, formats, deliverables

Section 5: Style Direction

  • References, preferences, boundaries

Section 6: Working Relationship

  • Communication, revisions, approval

Length Guidelines:

  • Comprehensive enough to be clear
  • Not so long it overwhelms
  • One page for simple projects
  • 2-3 pages for complex sets
  • Visuals don't count toward length

Common Brief Mistakes

Avoid these problems.

Too Vague:

Problem: "I want a happy emote"

Better: "Laughing expression with closed, curved eyes and open smile. Use for when chat is being funny. Similar energy to the attached reference but with my character's features."

Too Restrictive:

Problem: Specifying every single detail leaves no room for artistic interpretation

Better: Define key requirements, indicate where artist creativity is welcome

Missing Context:

Problem: No information about when/how emotes are used

Better: Brief explanation of use case for each expression

Conflicting References:

Problem: Providing references that show different styles without indicating preference

Better: Note which elements you like from each reference

No Flexibility:

Problem: Everything treated as equally critical

Better: Indicate priorities and where artist judgment is trusted

Using the Brief During the Project

The brief serves ongoing purpose.

Reference Point:

During revisions:

  • Check feedback against original brief
  • Stay focused on initial requirements
  • Avoid scope creep beyond brief
  • Use brief language consistently

Evaluation Standard:

When reviewing work:

  • Does it match brief requirements?
  • Are priorities addressed?
  • Technical specs met?
  • Vision captured?

Communication Foundation:

For discussions:

  • Reference specific brief sections
  • Use established terminology
  • Build on shared understanding
  • Clarify ambiguities against brief

FAQ: Emote Design Briefs

How long should my brief be?

Long enough to be clear, short enough to be read. Simple single emote: half a page. Full emote set: 2-3 pages. Quality over quantity—clear information beats lengthy vagueness.

What if I don't know exactly what I want?

That's okay. Describe the feeling or problem. "I need something for when X happens but I'm not sure visually what that looks like" is valid. Ask artist for options or interpretation.

Should I show references from other artists?

Yes, with attribution and context. Artists understand you're showing style direction, not asking for copies. Note what specifically you like about each reference.

How specific should expression descriptions be?

Specific enough that two different artists would produce similar concepts. If description could be interpreted many ways, add clarity or references.

What if the artist doesn't follow the brief?

Reference the specific brief section. Professional artists appreciate clear feedback. If pattern continues, it's compatibility issue—find different artist.

Should I share my brief publicly?

Keep it between you and artist. Share examples of good briefs to help others learn, but specific project briefs are working documents.

Building Your Brief Template

Create reusable format.

Template Components:

  • Standard sections
  • Fill-in areas
  • Reference attachment section
  • Technical specs pre-populated
  • Customizable per project

Evolution:

After each project:

  • What information was missing?
  • What was unnecessary?
  • How can brief improve?
  • Update template

Efficiency:

Good template saves time:

  • Consistent format
  • Nothing forgotten
  • Quick to customize
  • Professional presentation

Use EmoteShowcase's preview tool to share emote concepts with artists and verify designs throughout the commission process.

Effective design briefs transform commission relationships from frustrating guesswork to collaborative creation. The time invested in clear communication pays dividends in satisfaction—yours, the artist's, and ultimately your community's when they get to use emotes that match exactly what you envisioned.

Start with the essential components, add detail where helpful, and refine your approach with each project. Your brief-writing skills will improve alongside your emote collection.