Standard image formats: JPG, PNG, WebP. High-quality originals give better results than compressed screenshots.
How-to guide
Upload vs Describe
Show it or say it? The answer changes everything about your output quality.
⏱ 3 min readUpload a reference when you want to match an existing style. Describe from scratch when you want something new. Combine both for maximum control.
Users who discover reference uploads get more consistent results, fewer retries, and higher satisfaction. It's the single biggest quality unlock most beginners miss.
| Describe Only | Upload + Describe |
|---|---|
| Madison interprets your words | Madison sees what you mean |
| More creative variation | More predictable consistency |
| Good for new ideas | Good for matching existing work |
The Decision Framework
📎 Upload when...
- You have a reference image you want to match
- You need consistent style across multiple outputs
- You want to edit or build on an existing image
- "I want something like THIS" is easier than describing it
- You're working with specific products or brand assets
✍️ Describe when...
- You're starting from a blank canvas
- You want creative exploration and surprise
- The concept is abstract or doesn't exist yet
- You can articulate the vision clearly in words
- You're brainstorming and want variety
🔗 Best of Both: Upload + Describe
The most powerful approach combines both. Upload a reference, then describe what to change. This gives Madison a visual anchor AND creative direction. Fewer retries, more precision.
Upload + Describe Example
[Upload: your reference image]
"Match this lighting and composition style,
but change the subject to [new subject]
and shift the color palette to warm earth tones."
What Makes a Good Reference?
| Good References | Weak References |
|---|---|
| Clear composition and lighting | Blurry or low-resolution images |
| The specific style you want to match | Collages with mixed styles |
| One dominant mood or aesthetic | Busy images with too many elements |
| Real product/brand photos | Screenshots with UI elements |
Common Use Cases
| Scenario | Best Approach |
|---|---|
| "Make my product look premium" | Upload product photo + describe the scene |
| "I love this aesthetic, recreate it for my brand" | Upload reference + describe brand-specific changes |
| "Create something totally new" | Describe from scratch, iterate from results |
| "Same style as last time, new composition" | Upload previous output as reference |
| "Put my product in a lifestyle setting" | Save product as Element + describe scene |
Copy-Paste Templates
Reference-Guided Generation
[Upload reference image] Match the style, lighting, and composition of this reference. Subject: [your subject]. Setting: [your environment]. Keep the same mood but adapt for [your brand/purpose].
Style Transfer
[Upload style reference] Apply this visual style to a new scene: [describe your scene in detail]. Maintain the color palette and lighting approach from the reference.
Product in Context
[Upload product photo] Place this product in a [describe environment]. Lighting: [style]. Mood: [tone]. Ratio: [platform].
💡 Pro Tip: Elements for Recurring Subjects
If you frequently use the same products or characters, save them as Elements (Products or Cast). Madison will recognize them by name in future prompts, no need to re-upload every time.
Yes. Multiple references help when you want to combine elements from different sources: one for composition, another for color palette.
No. References guide style, composition, and mood, not pixel-perfect replication. Describe what specifically to match or change.
Not necessarily. Use references when consistency matters. Describe from scratch when you want creative exploration.
In Chat: use the attach button (+) next to the message input. In Studio: use the reference image field. On Telegram: send the image directly in the chat.
What to try next
Ready to create?
Start generating professional ads with Madison in minutes.
Free to start. No credit card required.