Sharing Files and Images
Sometimes explaining with words isn’t enough. That’s why you can share files and images directly with Claude!
How to attach files
Section titled “How to attach files”The attachment button
Section titled “The attachment button”Look for the 📎 paperclip icon next to your message box:
-
Tap the paperclip 📎
-
Choose what to share:
- 📸 Take a photo
- 🖼️ Choose from photos
- 📁 Browse files
- 📄 Select from your space
-
Add your message and send
What you can attach
Section titled “What you can attach”Images
Section titled “Images”- Screenshots of errors
- UI designs you want to build
- Diagrams or flowcharts
- Whiteboard sketches
- Any photo from your device
- Code files from your space
- Configuration files
- Log files
- Text documents
- Data files (JSON, CSV, etc.)
Sharing screenshots
Section titled “Sharing screenshots”Screenshots are super helpful for:
Error messages
Section titled “Error messages”Instead of typing out an error:
- Take a screenshot
- Attach it
- Say “Help me fix this error”
Claude can read the error and see the context!
UI issues
Section titled “UI issues”Show Claude what you’re seeing:
- “This button isn’t aligned right”
- “The layout breaks on small screens”
- “This doesn’t match my design”
Code snippets
Section titled “Code snippets”If you see code elsewhere:
- Screenshot it
- Ask Claude to explain
- Or implement something similar
Sharing code files
Section titled “Sharing code files”From your current space
Section titled “From your current space”The file browser shows your workspace:
- Tap 📁 Browse files
- Navigate to your file
- Select and attach
- Ask your question
Multiple files
Section titled “Multiple files”You can attach several files at once:
- Related components
- Config and code together
- Test files with source files
Large files
Section titled “Large files”Claude can handle big files:
- Shows relevant portions
- Focuses on what matters
- Summarizes if needed
Smart context sharing
Section titled “Smart context sharing”Claude remembers attachments
Section titled “Claude remembers attachments”Once you share a file, Claude knows about it for the whole conversation:
You: [Attach app.js] "This file has a bug"Claude: "I see the issue on line 23..."You: "What about the function on line 45?"Claude: "Looking at line 45 of app.js..."Comparing files
Section titled “Comparing files”Share multiple files to compare:
- “What’s different between these configs?”
- “Which component is better?”
- “How can I merge these functions?”
Working with images
Section titled “Working with images”Claude can see
Section titled “Claude can see”Claude understands images like:
- Code in screenshots – Can read and recreate
- Error messages – Understands and explains
- UI layouts – Can describe or recreate
- Diagrams – Understands flow and structure
Image examples
Section titled “Image examples””Build this UI”
Section titled “”Build this UI””- Attach a design screenshot
- Say “Create React components for this”
- Claude writes matching code
”Explain this diagram”
Section titled “”Explain this diagram””- Attach a flowchart photo
- Ask “How would I implement this?”
- Get step-by-step guidance
”Fix this visual bug”
Section titled “”Fix this visual bug””- Screenshot the broken UI
- Say “This doesn’t look right”
- Claude identifies and fixes issues
Best practices
Section titled “Best practices”Clear photos
Section titled “Clear photos”For best results:
- Good lighting for photos
- Clear screenshots (not blurry)
- Crop to relevant parts
- Include context when helpful
Descriptive messages
Section titled “Descriptive messages”Help Claude help you:
- ❌ “Fix this” [attachment]
- ✅ “This error appears when I click submit” [attachment]
Organize attachments
Section titled “Organize attachments”When sharing multiple files:
- Attach related files together
- Explain relationships
- Mention specific files in your message
Common scenarios
Section titled “Common scenarios”Debugging with screenshots
Section titled “Debugging with screenshots”“I’m getting this error [screenshot] when I try to save. The relevant code is here [attach save.js]“
Building from designs
Section titled “Building from designs”“Can you create components that look like this? [design screenshot] Use React and Tailwind CSS”
Code review
Section titled “Code review”“Could you review these files [attach multiple] and suggest improvements?”
Learning from examples
Section titled “Learning from examples”“I found this code online [screenshot]. Can you explain how it works and help me adapt it?”
Privacy notes
Section titled “Privacy notes”Your attachments are private
Section titled “Your attachments are private”- Only you and Claude see them
- Not stored permanently
- Not used for training
- Stay within your conversation
Sensitive information
Section titled “Sensitive information”Be mindful of:
- Passwords in config files
- API keys in code
- Personal data in screenshots
- Private business logic
Attachment status
Section titled “Attachment status”Watch for indicators:
- 📎 Attached – Ready to send
- ⏫ Uploading – In progress
- ✅ Uploaded – Claude can see it
- ❌ Failed – Try again
Tips for success
Section titled “Tips for success”Context is king
Section titled “Context is king”- Explain what the attachment shows
- Point out specific areas
- Describe what you want
Combine with questions
Section titled “Combine with questions”- “Here’s my error [screenshot]. What causes this?”
- “This is my current UI [image]. How can I add a dark mode?”
Let Claude explore
Section titled “Let Claude explore”- “What issues do you see in this code?”
- “How would you improve this design?”
- “What’s interesting about this file?”
Next steps
Section titled “Next steps”Master more Claude features: