> For the complete documentation index, see [llms.txt](https://docs.brewersfriend.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.brewersfriend.com/profile/picture-and-profile.md).

# Public Profile

## Getting Started

Here we have information that will be on your public profile if it is public.

<https://www.brewersfriend.com/homebrew/profile/public>

### Profile Image

This image will appear on your public recipes and your profile (if you choose to make it public). We recommend you upload a profile image, even if you do not opt for a public profile.&#x20;

**KEEP IT CLEAN! No nudity, violence, hate symbols, etc. Otherwise, have fun and use your imagination!** \
\
Only .gif, .jpg and .png type images are allowed to be uploaded. (3MB max upload size).

### Enable Public Profile

Just a yes or no that establishes a profile page for your brewing account everyone can look at. Your profile contains your profile picture, brewing description, recipes you have flagged as public, and a breakdown of your brewing activity.

### About Me

* My Brewing
* My Beers
* My Location
* My Website
* My Facebook
* My Twitter
* My Google Plus (going away)


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.brewersfriend.com/profile/picture-and-profile.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.