Write for us: AI tools, image and video generators, avatars and synthetic media

EveryAny.One publishes guest posts from people who use AI tools and can show their work. If you have tested AI image generators, made video with AI, built an AI avatar or digital twin, or know the law and detection side of synthetic media, we would like to hear your pitch.

What we publish

We want pieces a reader could not get from a vendor's own page. The strongest pitches are one of these:

• Hands-on tests of AI tools. The same prompts run through several AI image generators or AI video generators, with every output shown and the settings recorded.
• Practical guides. How to get a usable result from an AI avatar, talking-avatar video or AI character tool, step by step, with your own screenshots.
• Prompt guides that work. Prompts for realistic images, text in images, product shots or consistent characters, with the outputs that prove them.
• Synthetic media and the rules. Deepfake detection, content provenance, likeness and consent, and AI regulation, from practitioners, researchers or lawyers, sourced to primary documents.
• Case studies. How a team actually uses AI image, video or avatar tools in its work, including what it costs and what went wrong.

Published pieces go on the blog. Tool facts such as prices and free plans are kept in the tool listing, where each one carries its source and date.

What we do not publish

• Lists of AI tools nobody has used, or articles rewritten from other reviews or vendor marketing.
• Articles generated by AI and lightly edited.
• Anything about tools for explicit, "uncensored" or non-consensual imagery, or AI companion and girlfriend apps.
• Product announcements, press releases, or pieces written to promote one tool.
• Topics outside AI image, video, avatar, character and synthetic media tools.

Guidelines

A guest post meets the same standard as our own work, set out in our methodology.

• Original and unpublished, here or anywhere else, and not published elsewhere afterwards.
• Show the evidence. Your own screenshots and outputs, with the date you made them and the plan you were on.
• Source every fact. Prices, free limits and terms come from the vendor's own page, with the date you read it.
• Say what you tested and what you did not. Do not describe a tool's output quality unless you used it.
• Length: usually 1,200 to 2,500 words; long enough to be useful, no longer.
• Plain English, short paragraphs, and an answer near the top. We edit for accuracy, clarity and house style, and send you the edit before it goes live.

Links, disclosure and money

We do not charge to publish and we do not sell links. Links in a guest post are there to support a claim, usually to a vendor's documentation or a primary source, and we remove any that are not. Your byline carries a short bio and one link to your own site or profile. If you work for, are paid by, or have an affiliate relationship with any tool the piece mentions, say so in the pitch; we publish that disclosure with the article. See our disclosure page.

Pitch us

Send a headline, a short outline and what you tested or know first-hand. Do not send a finished draft yet: we agree the angle first. You can also email [email protected].