There was a time when waiting for a highly anticipated book meant exactly that: waiting.
You might have seen the cover in a bookstore catalog. Perhaps your local bookseller had a poster in the window. If you were particularly devoted, you might have clipped an interview from a magazine or read a short excerpt released by the publisher and then you waited for publication day.
Today, waiting looks very different. Readers track ISBN registrations. They examine retailer listings in different countries. They watch publishers’ websites for changes, inspect images, compare metadata, follow authors across multiple social platforms, analyze deleted posts, and sometimes even look through the code behind a website for clues.
When something appears online before an official announcement, it can spread across TikTok, Reddit, Instagram, Facebook and private fan groups in minutes. By the time someone realizes, Perhaps we weren’t supposed to see that yet, thousands of people already have.
That is exactly why a debate currently moving through the fantasy-reading community deserves a closer look. Not because readers are too enthusiastic. Not because fandom has somehow gone wrong. But because in an era when information can escape long before publication day, we may need to reconsider an increasingly complicated question:
Just because we can see something, does that mean we should share it?
The ACOTAR Question
Few book releases illustrate the intensity of modern fandom quite like Sarah J. Maas’s A Court of Thorns and Rosesseries.
Readers have waited years for the continuation of the story, and anticipation for the next books has been extraordinary.
Bloomsbury has officially announced that A Court of Splintered Harmony will be published October 27, 2026, followed by A Court of Forgotten Melody on January 12, 2027. The books form what the publisher is calling The Valkyrie Cycle.
But even the official reveal demonstrated how difficult it has become to control information surrounding an enormously anticipated book.
Before Sarah J. Maas formally shared the covers and titles on August 17, fans online were already discussing images and titles they said had been discovered through her website and its underlying code. Around the same time as the official reveal, descriptions appeared through major retailers.
The formal announcement itself was clearly much larger than a single social-media post. Maas revealed the books publicly, retailers updated their listings, and digital billboards appeared in Los Angeles, Denver and New York.
Yet by then, some fans had already seen pieces of the reveal. Was that a leak? Was it simply excellent internet sleuthing? Was information accidentally made publicly accessible a few hours too soon? Those questions were never quite as simple as social media made them sound.
Then, on September 12, the discussion became even more complicated. Fans discovered an audiobook sample for the forthcoming book on the official RBmedia website. People listened. Screenshots circulated. Discussions immediately appeared online. Later, the sample disappeared from the page.
RBmedia had already officially announced in August that Elizabeth Evans would narrate the two forthcoming ACOTAR audiobooks, so the publisher’s involvement with the project itself was certainly not secret. What remains unclear, as of this writing, is why that particular sample appeared when it did. There has been no public explanation that I can find confirming whether its brief appearance was intentional promotion, a technical error, or an accidental early publication. And that uncertainty is precisely what makes the situation so interesting.
Because once information appears on an official website—even briefly—what exactly are readers looking at? A leak a preview, a mistake or simply information that arrived ahead of schedule?
First, We Need to Stop Calling Everything a “Leak”
The word leak gets used very loosely online. But not every piece of information that appears before an author’s planned announcement is the same thing. There is an important difference between several scenarios.
An Official Reveal
This is the straightforward one. The author, publisher or authorized partner intentionally releases information: a cover, title, synopsis, excerpt, narrator announcement, sample chapter or promotional image. The information is meant to be shared. Go forth and theorize.
A Retailer Slip
Large publishing releases involve enormous numbers of people and systems. Publishers send metadata to bookstores, wholesalers, libraries, audiobook distributors, online retailers and international partners. Product pages have to be created. Covers have to be uploaded. Descriptions have to be entered. Publication dates, ISBNs and formats have to move through databases. Occasionally, something becomes visible earlier than intended. But what happens next is where the ethical question begins.
A Platform or Publisher Error
This is even more complicated. Suppose an excerpt, sample or image appears on the website of the company actually producing or distributing the book. It is publicly accessible. There is no hacking involved. No password has been bypassed. No confidential file has been handed over by an employee. A reader clicks a button and hears something that is sitting on a public webpage. Can we reasonably accuse that reader of wrongdoing? I don't think so. But discovering something and redistributing it after it has been removed are two different actions. That distinction matters.
A Genuine Leak
A true leak is different. This might involve someone receiving advance material through employment, publishing, bookselling, printing, distribution, reviewing or another privileged position and deliberately releasing material that was never authorized for public distribution. It could involve photographs of pages, unreleased manuscripts, audio files, screenshots from restricted systems or entire sections of a book. That is much closer to what most of us traditionally mean when we use the word leak. And it raises very different questions from a fan discovering an accidentally public retailer page.
Finding Something Is Not the Same as Spreading It
This may be the most useful distinction in the entire debate. Curiosity is human. Fantasy readers may be especially susceptible to it because we have essentially been trained by the books we love to look for clues. We search maps, we analyze prophecies we remember tiny details from three books ago because perhaps that strange silver ring will matter later, we notice symbols, we compare editions, we speculate about characters whose names appeared in two sentences six years ago. Give a community like that an unfinished website and tell them one of the most anticipated fantasy releases in the world is coming?Someone is going to investigate. I don't find that surprising, and I don't find curiosity itself particularly troubling.
But there is a moment after discovery when a choice occurs. Do I look? Do I share? Do I put the information behind a spoiler warning? Do I post the actual material? Do I tell people where to find a copy after the original has been taken down? Do I place the revelation directly into a TikTok thumbnail where thousands of readers will see it before they can possibly choose to scroll away?
Those are different decisions.
And perhaps our conversations about leaks would be more productive if we stopped treating all of them as though they were the same.
The Reader Who Does Not Want to Know Matters Too
There is another person who tends to disappear from debates about leaks: the reader who doesn't want the information. Some readers want everything. Give them the cover, the character theories, the seventy-eight-frame TikTok analysis of a shadow appearing behind someone's shoulder. Give them every official excerpt the publisher releases. If something questionable appears online, they may want that too. There is nothing inherently wrong with wanting to know. But another reader may have waited five years for a book and want to experience the opening pages for the first time while holding the finished novel.
That person has just as much right to enjoy fandom as everyone else. And the problem with social media is that opting out has become extraordinarily difficult. A traditional spoiler is usually something that happens after a book, movie or television episode is released. The audience theoretically had an opportunity to encounter the story first. Premature information reverses that relationship.
Now readers can be spoiled before the book even exists for them to read. They cannot simply hurry home and finish it. They cannot log off until tomorrow and catch up. Publication may be six weeks away.
That changes the etiquette considerably.
Spoiler Warnings Are an Act of Courtesy, Not Censorship
Some people become oddly defensive about spoiler warnings. "If you don't want spoilers, stay off the internet." That sounds practical until we consider what it actually asks.
Should someone have to leave every fantasy community for months because other people want to discuss unreleased information? Keeping major revelations out of thumbnails allows people to decide whether they want to continue.
A simple: Potential unreleased ACOTAR information below. Proceed only if you want to see it is enough. The people who want every scrap of information can enthusiastically enter. The people who don't can leave. Nobody loses. That isn't censorship. It's hospitality. And book communities, at their best, should be hospitable places.
But Publishers Have Changed the Game Too
It would be unfair to put the entire responsibility on fans. Modern publishing has become extraordinarily good at manufacturing anticipation. This is not necessarily criticism. Anticipation is part of marketing, and done well, it can be tremendous fun. A cover reveal becomes an event. An author's social feed suddenly disappears. A mysterious symbol appears. A countdown begins. A special edition is teased. Readers are encouraged to speculate.
Publishers know fandom communities will search for meaning because that participation generates excitement. And when a beloved series has been quiet for years, even the smallest piece of information can become valuable. The result is a curious tension. Readers are encouraged to become detectives—but only up to a certain point. Look for clues just not that clue. Inspect the website but perhaps not that deeply. Speculate wildly but don't find the file we accidentally uploaded yesterday.
That boundary is not always obvious from the reader's side and publishing's increasingly complicated digital infrastructure makes perfect secrecy nearly impossible. An upcoming book may involve the author, agent, publisher, printers, distributors, retailers, audiobook producers, narrators, librarians, translators, foreign publishers, publicity teams and countless technology systems.
The more anticipated the book, the more people are watching every one of those systems. Eventually, something may appear.
Does Premature Information Actually Hurt a Book?
For a phenomenon as large as ACOTAR, an early cover sighting is unlikely to make readers suddenly cancel their plans to buy the novel. If anything, sudden information can create extraordinary attention but sales are not the only consideration. Authors and creative teams spend years building books. Publishing teams may spend months planning precisely how those books will enter the world. A cover reveal isn't merely an image uploaded to Instagram. It can involve designers, publicists, booksellers, press outlets, advertising purchases, retailer coordination, events and carefully timed announcements. For the author, it may also be emotional.
There is a difference between knowing readers will eventually see something and getting to say: Here it is. I made this.
Anyone who creates things understands that feeling. Whether it is a novel, a painting, a handmade object or a song, there is joy in choosing when something finally leaves your hands and enters someone else's. An accidental reveal can take away a little of that moment. Even when no financial harm occurs.
There Is Also a Difference Between Information and the Work Itself
I think this line is especially important. A prematurely visible title is one thing. A cover is another. A publisher-written synopsis is another. A chapter of an unpublished novel is something else entirely. The closer we get to the creative work itself, the more cautious we should become. A title tells us something about a book. A full unpublished passage is the book. An audiobook chapter is not merely news about the story. It is part of the story.
Once an original source disappears, continuing to distribute copies, recordings or transcriptions crosses a much more significant line than discussing the fact that the material briefly existed. That is why this article does not reproduce or describe the contents of the recently circulated ACOTAR audio. The interesting story here is not what the sample revealed. It is what happened around it.
When Fandom Becomes a Race
There is another force driving all of this that rarely gets discussed: being first has value now.
The first TikTok account to reveal something may receive enormous traffic. The first Instagram page with a screenshot can gain followers. The first Reddit thread becomes the place everyone links. The first creator to explain "WHAT THIS MEANS FOR ACOTAR 6" may receive tens or hundreds of thousands of views. That creates an incentive that didn't exist when readers simply discussed books with friends. Information is now content and content has currency.
Suddenly the decision to pause and ask, Should I post this?, is competing against the knowledge that somebody else probably will. That doesn't make book creators villains. It does mean the ecosystem rewards speed much more strongly than reflection. Perhaps that is part of why today's spoiler culture feels different.
A Better Kind of Fandom Etiquette
Perhaps we don't need complicated rules.
Maybe we simply need a little generosity. If you discover something early, enjoy the thrill. If you choose to discuss it, make the choice clear to everyone who follows you. Use spoiler warnings. Keep revelations out of titles and thumbnails. Don't assume that "everyone has already seen it." If the original material is removed, think carefully before uploading copies of it somewhere else. Differentiate between discussing the existence of prematurely released material and redistributing the material itself. And most importantly, remember that another reader's choice not to know is every bit as valid as your choice to look.
The same courtesy should extend after publication. Not everyone can read a 700-page fantasy novel at midnight on release day. Some readers have jobs. Some have children. Some are waiting for library copies. Some require accessible editions. Some live in countries where the book arrives later.
A fandom shouldn't require Olympic-level scrolling reflexes merely to remain unspoiled.
So Who Is Responsible?
Probably everyone. Publishers have a responsibility to secure unreleased material and manage their digital systems carefully. Retailers and distribution partners have a responsibility to respect embargoes and publication schedules. People with privileged access have an obvious obligation not to distribute work entrusted to them. Creators and fan accounts can decide whether being first is more important than giving their audience a choice. And readers can distinguish between stumbling across something interesting and deliberately circulating something that was clearly withdrawn.
That doesn't require policing fandom. It requires participating in it thoughtfully.
Anticipation Is Part of the Magic
The fantasy community's extraordinary enthusiasm is not something I want to see diminished. Quite the opposite. There is something wonderful about thousands of readers caring enough about fictional worlds to spend hours discussing them. We make theories, argue affectionately over characters, choose courts and houses and factions, buy midnight editions reread thousands of pages looking for clues we missed. We send one another increasingly unhinged messages containing nothing more than a screenshot and twelve exclamation marks.
That joy is real and after years of waiting, ACOTAR readers have every reason to be excited. But excitement doesn't have to mean consuming every piece of information the instant it becomes available. Sometimes anticipation deserves to exist too. There was a reason we once stared at unopened presents under the Christmas tree. We technically knew we could tear away the paper. But waiting was part of the experience. Books may deserve a little of that mystery. Perhaps the question isn't whether fans should search for clues. Of course we will. We're readers. Looking for hidden meaning is practically part of the job description.
The more meaningful question may be what we do once we discover something we weren't expecting to find because there is another reader beside us who may not want to know yet; and perhaps preserving that person's surprise is one small kindness we can offer each other.
In a world where almost everything can be discovered instantly, not knowing has become something rare, maybe even something magical.
Join the Conversation
Where do you fall when it comes to highly anticipated books?
🔮 Give me every clue, theory and early discovery.
🌙 I only want information officially released by the author or publisher.
🙈 Don't even show me the synopsis—I want to go in completely blind.
⚔️ I'll look at early information, but I won't spoil it for anyone else.
And the bigger question:
If unreleased book material accidentally appears on an official publisher or retailer website, do you consider it a leak?
I'd genuinely love to know what other readers think.
The Sidra Journal welcomes spirited bookish discussion, but not spoilers. Please keep any discussion of unreleased story content out of the comments.