Skip to main content

Navigate Footly: buyer mode, creator mode, settings, and support

A quick tour of the main Footly areas so buyers and creators know where to browse, post, message, and get help.

Footly has a few core areas that matter most: browsing and buying, creator tools, messaging, settings, and support. The exact labels may vary as the product evolves, but this guide gives you the mental map to find what you need quickly.

For buyers

Browse public profiles: Start with public creator profiles and teaser posts to understand style, quality, and price before buying.

Review paid offers: Read the description on subscriptions, collections, videos, PPV messages, or custom offers before purchasing.

Use messages respectfully: Ask clear questions, share what you are looking for, and respect creator boundaries and response times.

Check purchases: Keep track of content you bought, active subscriptions, and any custom request conversations.

For creators

Profile: Add a clear display name, bio, public teaser content, and a profile link you can share.

Uploads: Post public teasers for discovery, then reserve full sets, full videos, and higher-value content for paid posts or PPV.

Messages: Stay active with viewers and potential buyers. Many sales come from helpful, direct conversations, not only public posts.

Buyer Discover: Use Buyer Discover to find potential buyers, start conversations, and turn interest into offers.

Settings: Check payout, account, privacy, and support settings before promoting heavily.

Where to get support

Open Settings: Use the Settings page when you need account options or support access.

Click Get support: The support button opens Footly support from both mobile and desktop.

Include details: Share the account email, relevant creator username, purchase date, screenshot, or error message when useful.

Best practice

If you are not sure where a feature lives, start in Settings for account/support items, messages for conversations, and creator tools for posting, pricing, and profile setup.

Did this answer your question?