Skip to main content
Multimodal support lets Mem0 extract facts from images alongside regular text. Add screenshots, receipts, or product photos and Mem0 will store the insights as searchable memories so agents can recall them later.
You’ll use this when…
  • Users share screenshots, menus, or documents and you want the details to become memories.
  • You already collect text conversations but need visual context for better answers.
  • You want a single workflow that handles both URLs and local image files.
Mem0 passes images straight to your configured vision model, so per-image size and resolution limits come from that provider (for example, OpenAI caps images at 20 MB). Compress or resize large files to stay within your provider’s limits and keep processing fast.

Feature anatomy

  • Vision processing: Mem0 runs the image through a vision model that extracts text and key details.
  • Memory creation: Extracted information is stored as standard memories so search, filters, and analytics continue to work.
  • Context linking: Visual and textual turns in the same conversation stay linked, giving agents richer context.
  • Flexible inputs: Accept publicly accessible URLs or base64-encoded local files in both Python and JavaScript SDKs.
FormatUsed forNotes
JPEG / JPGPhotos and screenshotsDefault option for camera captures.
PNGImages with transparencyKeeps sharp text and UI elements crisp.
WebPWeb-optimized imagesSmaller payloads for faster uploads.
GIFStatic or animated graphicsWorks for simple graphics and short loops.

Configure it

You must set enable_vision: True in your LLM config for image content to be processed. Without it, image turns are silently dropped and no vision memories are created. Example:
vision_details maps to the vision model’s image detail setting and accepts "auto" (the default), "low", or "high". Use "high" for dense images like receipts or documents; "low" is faster and cheaper for simple photos.

Add image messages from URLs

Inspect the response payload: the memories list should include entries extracted from the menu image as well as the text turns.

Upload local images as base64

Smaller images upload and process faster. Compress or resize before encoding to base64, and check your vision provider’s per-image size limit for large files.

See it in action

Restaurant menu memory

The response should capture both the allergy note and menu items extracted from the photo so future searches can combine them.

Document capture

Combine the receipt upload with structured metadata (tags, categories) if you need to filter expenses later.

Error handling

Fail fast on invalid formats so you can prompt users to re-upload before losing their context.

Verify the feature is working

  • After calling add, inspect the returned memories and confirm they include image-derived text (menu items, receipt totals, etc.).
  • Run a follow-up search for a detail from the image; the memory should surface alongside related text.
  • Monitor image upload latency: large files should still complete under your acceptable response time.
  • Log file size and URL sources to troubleshoot repeated failures.

Best practices

  1. Ask for intent: Prompt users to explain why they sent an image so the memory includes the right context.
  2. Keep images readable: Encourage clear photos without heavy filters or shadows for better extraction.
  3. Split bulk uploads: Send multiple images as separate add calls to isolate failures and improve reliability.
  4. Watch privacy: Avoid uploading sensitive documents unless your environment is secured for that data.
  5. Validate file size early: Check file size before encoding to save bandwidth and time.

Troubleshooting

IssueCauseFix
Upload rejectedImage exceeds your vision provider’s size limitCompress or resize before sending.
Memory missing image dataLow-quality or blurry imageRetake the photo with better lighting.
Invalid format errorUnsupported file typeConvert to JPEG or PNG first.
Slow processingHigh-resolution imagesDownscale or compress to under 5 MB.
Base64 errorsIncorrect prefix or encodingEnsure data:image/<type>;base64, is present and the string is valid.

Connect Vision Models

Review supported vision-capable models and configuration details.

Build Multimodal Retrieval

Follow an end-to-end workflow pairing text and image memories.