> For the complete documentation index, see [llms.txt](https://help.maearth.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.maearth.com/resources-for-land-stewards/project-profile/image-guide.md).

# Image Guide

Your photos (or videos) are often the first thing supporters see. They help people connect with your work, understand your context, and feel the land. You can update images and videos at any time in your project header or project story.

**Engaging images:**

* Show the actual project and the land where it is taking (or will take) place
* Include people engaged in the project
* Feel authentic and grounded
* Invite people into your story

### Five tips for compelling project images

#### 1. Organic, not artificial

**Show real life, not staged scenes.**

✅ **Yes:**

* Workers with muddy hands planting seedlings
* Natural lighting and outdoor settings
* Tools being used, work in progress
* Candid moments of people actually working

<figure><img src="/files/ClDKQgIPtkjMc7bNiaCa" alt="" width="375"><figcaption></figcaption></figure>

❌ **No:**

* Studio-style portraits with perfect lighting
* Overly edited or filtered photos
* Stock photos (generic)
* AI images

<figure><img src="/files/EZj4kCarPJR9vUgrUZiN" alt="" width="375"><figcaption></figcaption></figure>

#### 2. Show people

**There are people involved in your nature project. Show them.**

✅ **Yes:**

* Team members working together
* Community gatherings around the project
* People's faces and expressions
* Hands doing work (planting, building, harvesting)
* Multiple generations when relevant

<figure><img src="/files/SeJXdkVJRnHrjNiZmYYN" alt="" width="375"><figcaption></figcaption></figure>

❌ **No:**

* Only landscape shots with no people
* People too distant to see
* Only formal group photos where everyone poses

<figure><img src="/files/Y919cztHxXNyMsvyHRFJ" alt="" width="375"><figcaption></figcaption></figure>

#### 3. Authentic, not perfect

**Show genuine moments, not manufactured ones.**

✅ **Yes:**

* Candid working shots
* Real expressions (concentration, joy, effort)
* Natural poses, people doing actual tasks

<figure><img src="/files/3kJSdz1lPeWmEe6mEw79" alt="" width="375"><figcaption></figcaption></figure>

❌ **No:**

* Obviously staged "pretending to work"
* Perfect coordination that feels unnatural
* Overly formal or stiff poses

<figure><img src="/files/OdMhMoVMEDMIoDhV5vFY" alt="" width="375"><figcaption></figcaption></figure>

#### 4. Natural, not sleek

**Embrace the rough edges of real work.**

✅ **Yes:**

* Natural lighting (morning/evening light is beautiful)
* Real work environments (muddy, dusty, imperfect)
* Worn tools, working clothes

<figure><img src="/files/hmahD0zjUuzRFdpgt5hc" alt="" width="375"><figcaption></figcaption></figure>

❌ **No:**

* Heavy filters or artificial color enhancement
* Perfectly clean and coordinated everything
* Overly stylized or artistic compositions

<figure><img src="/files/vYb3ORj3DqW3uEA3FbXk" alt="" width="375"><figcaption></figcaption></figure>

***

#### 5. High resolution

**Technical quality matters for usability.**

✅ **Yes:**

* At least 1200x800 pixels (landscape orientation)
* Clear focus on subject
* Good lighting (not too dark or blown out)
* Properly exposed (not too dark or bright)

❌ **No:**

* Blurry or out-of-focus shots
* Too small (pixelated when enlarged)
* Extreme shadows or overexposure
* Screenshots from video (usually too low quality)

**How to check:** Look at the image at full size on your phone or computer. If it looks clear and detailed, it's probably high enough resolution.

**Phone cameras work great:** Modern phone cameras capture plenty of resolution. Just make sure lighting is good and subject is in focus.

#### 6. Include videos!

Video is a great way to engage potential supporters, share more deeply about your project, and make your project story even more dynamic.&#x20;

Videos may be uploaded to your project header in lieu of an image, or incorporated into your project story by embedding a YouTube link.

***

#### Quick photo checklist

Before uploading images, ask:

* [ ] Can I see people clearly?
* [ ] Does this show actual work happening on the land?
* [ ] Is this authentic?
* [ ] Is the resolution high enough?
* [ ] Does this help people understand my project?
* [ ] Would I want to see this if I were deciding whether to contribute?

***

#### Don't have great photos yet?

**That's okay. You can:**

**Take new photos:** Next time you're working, ask someone to take photos.

**Use what you have:** Even imperfect photos showing real work are better than no photos or stock images.

**Ask your community:** Team members or supporters might have photos from site visits or community days.

***

#### Remember

**You don't need professional photography.**

We're looking for authentic documentation of real work. Phone camera photos taken by team members are perfect.

What matters most:

* Real people
* Actual work
* Your authentic story
* Clear enough to see what's happening

**Show the reality of regeneration work.**


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.maearth.com/resources-for-land-stewards/project-profile/image-guide.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.