Storyblocks does not pay a fixed rate per download. It pays a share of a Member Library Revenue Pool, and your share is set by how much of your content was downloaded relative to every other contributor in the same period. The pool's size is not published, and the agreement behind the programme says the method used to size it is proprietary.
What you are actually being paid from
Storyblocks' contributor FAQ keeps this deliberately high level. The company says it shares a percentage of its subscription revenue, and that your earnings depend on how often your content is downloaded compared with other contributors' content. It does not state the percentage anywhere in the FAQ. The Member Library and Machine Learning Partner Program Agreement is where the mechanics are actually written down, and it is the document worth reading before you plan around any number.
Under that agreement the pool is adjusted at least quarterly and its exact calculation is proprietary. The text states plainly that the Member Library Revenue Pool size is not published. Storyblocks can also change the calculation method: it must give email notice, the change takes effect fifteen days later, and termination rights are attached to that notice. If what you want is a predictable rate per download, this is not that kind of programme, and no amount of portfolio tuning will make it one.
Two weighting rules inside the agreement matter more than they first appear. A download taken during a customer's free trial is counted at a ten-dollar subscription value rather than at zero, so trial traffic does feed your share. Enterprise and API downloads are weighted by the subscription fees behind them, which means the same clip can be worth materially different amounts depending on which customer took it.
The agreement also contains a worked example built on a sixty per cent share. That figure is illustrative. It is there to show how the arithmetic runs, not to state a rate, and reading it as your royalty percentage is the most common misreading of the document. The honest summary is that Storyblocks publishes the shape of the calculation and withholds the inputs.
The payment calendar, and the fifth-of-the-month trap
Member Library payments go out on or about the fifteenth of each month and cover the previous month's eligible earnings, so April's downloads are paid on 15 May. Payouts are processed through Tipalti, and the agreement is explicit that they are issued net of third-party processing fees.
The detail that costs contributors a whole month sits elsewhere. Storyblocks states that any changes made to your payment information after the fifth of the month may make you ineligible for that month's payment. If you are switching banks, moving countries, or changing from PayPal to a direct transfer, do it in the first few days of the month or plan to wait for the next cycle.
The Storyblocks payout cycle, month by month
The documented Storyblocks payout cycle: downloads accrue through the month, payment details lock on the 5th, the Member Library payment lands on or about the 15th for the prior month, under-threshold balances carry over, and the machine learning pool pays every six months.
There is a minimum threshold as well, and it depends on which payout method you picked rather than being a single company-wide figure. For Payoneer, Storyblocks lists a minimum of ten dollars per transaction. Anything under the threshold is not forfeited; it carries over into the next month's payment.
You can also hold payments on purpose. The FAQ says you may hold your payments indefinitely to help reduce third-party fees, which is a genuine strategy when your monthly balance is small, because the fee is charged per payout rather than per dollar paid.
The fee table nobody reads until the first payout
Storyblocks publishes the per-payout fees charged by the third parties that move the money, and they vary by an order of magnitude depending on the method you picked when you set the account up. These are the figures listed in its contributor FAQ:
- Payoneer, as a prepaid MasterCard or a global bank transfer: no fee, but a minimum payout of $10.00 per transaction.
- PayPal: $1.00 per payout.
- Direct Deposit: $1.00 per payout.
- Wire transfer inside the United States: $15.00 per payout.
- International wire transfer paid in US dollars: $25.00 per payout.
- International wire transfer paid in local currency: $20.00 per payout.
- Check: $6.00 per payout.
- eCheck: $5.00 per payout.
Those numbers are trivial in absolute terms and very large as a share of a small payout. A twenty-five dollar international wire against a forty-dollar month takes most of the month; the same wire against a thousand-dollar month is noise. Storyblocks also notes it may be legally required to withhold earnings for tax purposes and points contributors at its Tax Center, so the processing fee is not the only deduction sitting between the pool and your bank account.
Which Storyblocks payout method costs you least?
Walks the payout methods Storyblocks lists against its stated per-payout fees: no fee on Payoneer with a $10.00 minimum, $1.00 on PayPal and Direct Deposit, $15.00 on a US wire, $25.00 on an international wire in USD, $20.00 in local currency, $6.00 by check and $5.00 by eCheck.
The machine learning pool is a second payment on a different clock
The programme's full name gives this away: it is a Member Library and Machine Learning Partner Program. Alongside the subscription pool there is a generative AI side with its own two pools, a Dataset Pool and a Model-Product Pool. Your payout there depends on what percentage of the licensed dataset or trained model your content accounts for, multiplied by the relevant pool.
How much goes into the Dataset Pool is even less specified than the subscription side. The agreement says the contribution is a percentage of each dataset licence's value, to be determined by Storyblocks. These payments run every six months rather than monthly, on or about 15 June and 15 December, and they are subject to the same minimum payout threshold as everything else.
Whether that is a good trade is a judgement call, not a calculation, because you cannot see the inputs. What you can do is know it exists before you sign, rather than discovering a June payment line you did not expect.
What the agreement says about leaving
The main licence is non-exclusive, perpetual and worldwide, so contributing to Storyblocks does not stop you selling the same footage elsewhere. Music is the exception: for music you grant Storyblocks the sole and exclusive right to administer your tracks on platforms such as YouTube, Audible Magic, Facebook and Instagram for the term, including collecting ad revenue, and you are barred from monetising member use through Content ID or similar programmes.
Removal runs on a thirty-day clock. You give thirty days' written notice, and Storyblocks removes the content within thirty days of that notice. Customers who already downloaded a file keep their licence, and members can re-download your removed content for up to twelve months after the removal date, so the tail on a withdrawal is a year rather than a month.
The machine learning clause has no exit at all. Removal or termination does not stop the use of datasets or models that already include your content, the agreement states that models trained on datasets including your content cannot be untrained, and you covenant not to sue over that use. This is the part to decide on before you upload, because it is the one decision you cannot reverse later.
How this compares in shape to the agencies you already know
The useful comparison is not whose rate is higher, because Storyblocks does not publish one. It is whether you can forecast at all. Adobe Stock's payout model and Pond5's both give you something to multiply: a stated share or a stated price. A pool share divided among all contributors gives you a number only after the fact.
That changes what you should optimise. On a per-download agency, more files at a steady quality raises revenue roughly in line with volume. In a shared pool, your earnings move with your share of downloads, so a competitor flooding the library dilutes you even if your own download count holds. Volume still helps, but so does being in categories where the library is thin, which is why Storyblocks maintains an in-demand content list worth checking before you plan a shoot.
It also makes the metadata side matter in a specific way. In a pool model you are competing with other contributors for the same downloads, and search placement is what decides who gets them. Being correct and complete is not a tie-breaker here, it is the whole mechanism.
Before your first payout
Pick the payout method deliberately rather than accepting the default, because the fee is charged per payout and a wire can cost more than a slow month earns. Complete the tax paperwork early, since Storyblocks notes it may be required to withhold. Make any banking change before the fifth. And get the upload side right first: the Storyblocks upload workflow has a thirty-day tagging deadline that quietly deletes untagged content, and the keywording rules decide whether your clips surface at all. Nothing in the payout mechanics can rescue content that was never findable.
If you deliver to Storyblocks alongside other agencies, the practical problem is keeping one set of metadata correct against several rulebooks at once. Rastock generates titles, descriptions and keywords per agency policy and delivers over FTP to 10+ agencies, with per-agency delivery status rather than a single “sent” flag — see what the feature set covers, or the pricing page for the 14-day free trial, which does not ask for a card.
Frequently asked questions
How much does Storyblocks pay per download?
Storyblocks does not publish a per-download rate. It pays a share of a Member Library Revenue Pool, and your share is set by how much of your content was downloaded relative to other contributors. The agreement states that the pool's size is not published and that the method behind it is proprietary, adjusted at least quarterly. Any fixed figure you see quoted elsewhere is not from Storyblocks' own documents.
When does Storyblocks pay contributors?
Member Library payments are issued on or about the 15th of each month and cover the previous month's eligible earnings, so April's downloads are paid on 15 May. The generative AI side of the programme pays on a separate six-monthly schedule, on or about 15 June and 15 December. Both are subject to the minimum payout threshold set for your payment method.
What is the minimum payout on Storyblocks?
The threshold depends on the payout method rather than being one company-wide figure. Storyblocks lists Payoneer with a minimum of $10.00 per transaction. If your balance is below your method's threshold, it is not forfeited: it carries over to the next month's payment. You can also choose to hold payments indefinitely, which Storyblocks says can help reduce third-party fees.
Does Storyblocks charge fees on payouts?
Payouts are processed through Tipalti and issued net of third-party processing fees. Storyblocks lists them per payout: no fee on Payoneer subject to its $10.00 minimum, $1.00 on PayPal, $1.00 on Direct Deposit, $15.00 on a United States wire transfer, $25.00 on an international wire in US dollars, $20.00 on an international wire in local currency, $6.00 by check and $5.00 by eCheck.
Why did I miss a Storyblocks payment after changing my bank details?
Because of the date. Storyblocks states that any changes made to your payment information after the 5th of the month may make you ineligible for that month's payment. Changing a bank, a country or a payout method in the second half of the month will typically push the payment to the following cycle, so make banking changes in the first few days of the month.
Can I take my content back off Storyblocks?
Yes, with notice, but the tail is long. You give 30 days' written notice and Storyblocks removes the content within 30 days of that notice. Customers who already downloaded a file keep their licence, and members can re-download removed content for up to 12 months after the removal date. The machine learning clause has no exit: the agreement states that models trained on datasets including your content cannot be untrained.