Back to the blog

Artificial Intelligence

Midjourney Statistics: Verification Limits and AI-Image Metrics

Separate community members, website users and paid accounts. Review Midjourney data limitations and measure approved AI-image assets in your own workflow.

Justin McGill4 min read

AI-generated gouache example of a gardener inspecting a young plant in a rooftop greenhouse at sunrise
On this page
  1. Which Midjourney figures remain unverified here?
  2. Define the number before comparing it
  3. An example of incompatible denominators
  4. Measure the image workflow your team actually uses
  5. Bring approved visuals into the BrandWell content process
  6. Questions about AI-image statistics

Midjourney statistics need a named measure, reporting date and reliable source before they can support a business decision. Discord membership, website visitors, active users, generated images and paying customers are different counts. One cannot stand in for another.

The earlier version of this article combined historical estimates of users, traffic and revenue with unsupported technical and pricing claims. This review removes those figures rather than presenting them as verified current data. It also replaces a list of vendor promotion points with a practical way to evaluate AI-image usage in your own content workflow.

Which Midjourney figures remain unverified here?

We have not verified a current revenue total, paying-customer count or demographic breakdown for this article. The earlier server-membership figures did not establish paid adoption. Website-traffic estimates did not establish registered users. A projected annual revenue figure was also described elsewhere in the article as already earned.

The previous claims about a public API, two-second generation time, processing capacity and blockchain-based security are not supported by the evidence retained for this review and have been removed. Do not use this article as a statement of current vendor capabilities, prices or security practices.

Define the number before comparing it

  • Community membership: accounts belonging to a particular community at a stated time.
  • Website traffic: the specific visit or user measure in the report, with its estimation method.
  • Product activity: users or actions meeting a defined condition during a stated interval.
  • Paid customers: the paying-account definition used in the source.
  • Revenue: the period, currency and accounting basis, rather than an unlabeled projection.

Even within one analytics product, user measures differ. Google Analytics distinguishes total, active, new and returning users; its active-user definition includes specified engagement and event conditions. Preserve the exact measure in the report instead of renaming it a subscriber count. See Google’s user-metric definitions.

An example of incompatible denominators

Imagine a hypothetical creative community with 10,000 members, a website with 2,000 measured users in a month and 100 new paid accounts. Dividing 100 by 10,000 gives 1%, while dividing 100 by 2,000 gives 5%. Neither automatically establishes signup conversion: you first need to know which eligible visitors the paid accounts came from and whether the periods and identities match.

This is an arithmetic example, not a Midjourney statistic. The same discipline applies to reports about any product. Label the numerator and denominator before using a percentage in a headline.

Measure the image workflow your team actually uses

A marketing team can evaluate its own assignments without relying on a vendor’s popularity. Record the brief, number of candidates, review effort, approved assets and publication destination. Include corrections for composition, legibility, brand fit and misleading details.

AI-generated rooftop scene used as an editorial illustration
An AI-generated editorial example illustrates the topic. It is not a product screenshot, usage statistic or claim about a particular vendor.

For example, a hypothetical team reviews twelve candidate images and approves three. It spends $18 on generation and $72 on review. The cost per approved asset is $90 divided by three, or $30. The approval rate is 25%. These figures measure that example’s reviewed output, not a platform benchmark or a promised cost.

Bring approved visuals into the BrandWell content process

Use RankWell to develop the article brief and draft, then review the sources, media and search preview in the editor. Choose a visual because it explains the article’s topic or demonstrates the product accurately. An attractive generated picture should not be presented as evidence of a customer result or as a screenshot of functionality that does not exist.

Add descriptive alternative text and a caption when readers need context. Check the displayed crop on mobile and make sure any labels remain readable. Verify the image’s permitted use and keep approval responsibility with the appropriate person. This article does not claim that every external image-generation service has a native BrandWell integration.

Questions about AI-image statistics

Does a large community prove commercial adoption?

No. A community count measures its own membership definition. It does not establish paying customers or revenue.

Should an estimate be presented as a reported result?

No. Label estimates and projections clearly, identify the method and preserve the reporting date. Remove unsupported precision rather than adding a newer year to an old number.

What should a marketing team evaluate?

Evaluate relevant, approved assets and total review effort for your own assignments. Explore RankWell for the editorial workflow and review current BrandWell products for the wider platform.

Reviewed and updated October 3, 2026.

Written by

Justin McGill

Put your next growth opportunity to work.

Start with the product you need. Connect the work with AIMEE.