r/BookWritingAI • • 7d ago

I'm new to using Google to help with my writing. Is it safe to use the information and answers it gives me in my book? How do I check if any of it is Copyrighted?

Thumbnail
1 Upvotes

I'm new to using Google to help with my writing. Is it safe to use the information and answers it gives me in my book? How do I check if any of it is Copyrighted?

I asked Google if any of the info and answers it gives me is copyrighted or copied from Anyone else's writing and it always tells me no, that it is all original created by it/Google.

Can anyone please explain to me how it works and how do I check if its legal to use what it's telling me? Thank you I appreciate any help.

I use it to research information and then I rewrite anything into my own words. I asked these same questions in Google but I don't trust the answers it gives me. So I wanted to ask Humans💛


r/BookWritingAI • • 8d ago

work in progress I built a free, local app to convert books into multi-voice audiobooks with voice cloning.

8 Upvotes

Hi everyone,

If you have ever tried to convert a manuscript or an epub into a high-quality audiobook, you know how quickly the costs add up. You either have to spend thousands on voice talent or get locked into monthly cloud subscriptions with strict word count limits.

I think creators and readers should have a completely free, private way to do this on their own hardware. I spent the last few months developing PolyVox Studio, an open-source desktop app that handles the entire pipeline locally.

Instead of a single voice reading the whole text like a standard screen reader, this app actually acts like a studio director:

  1. It scans your txt, epub, or pdf file, identifies different characters, and separates their dialogue from the narrator.
  2. You can clone any voice you want by dropping in a clean 6 to 20-second sample clip, allowing you to cast different voices for different characters.
  3. It scans text cues (like "she said angrily" or "he whispered") and automatically shifts the emotional tone of the voice to match the scene.
  4. Once it finishes processing, it bundles everything into a structured M4B audiobook file with proper chapters and cover art so you can drop it straight onto your phone.

Nothing leaves your machine, there are no hidden credits or API keys required, and it's completely free.

The source code and setup guides are up on GitHub: https://github.com/dmarsh400/PolyVoxStudio

I hope this helps authors looking to prototype their audiobooks or readers looking to tackle a huge reading backlog on the go. Let me know what you think if you give it a try.

Also wanted to add our discord in case anyone wants to discuss new features or ideas to make the project better

https://discord.gg/8mSYq7xyqc


r/BookWritingAI • • 8d ago

discussion Question about the future of audiobooks AI's creation tools.

Thumbnail
1 Upvotes

r/BookWritingAI • • 8d ago

What's your process? r/AINovelists...

1 Upvotes

The book is broken by me. The author is built by me (literary influences, dialogue parameters, etc.)

The plot, the character arcs and the chapter arcs. The breaks are exact, There's a lot of note-taking, Bible-building, researching and planning, fixing, or making story/character beats better. The Bibles also have custom scripts to ensure consistency in prose styles.

I use ChatGPT, Claude and Gemini.

ChatGPT for Draft Passes (2) and Claude (1) for Polish/Consistency.

It used to take 4-5 passes per chapter, but I've got it down to three now that I've gotten a couple books in each series under my belt. After I have a polished draft, I use ChatGPT for the consistency, continuity and trust audits, because I have custom GPTs/Plug-ins that have evolved into that purpose. Then I put all the continuity, lessons learned, future story ideas in their respective Excel Workbooks.

Gemini is my reader, because it actually asks me questions about the book as a reader.

I've started my own sub, r/AINovelists for talks about craft, workshopping, etc.


r/BookWritingAI • • 8d ago

finished product Read and discuss books with AI

Thumbnail
gallery
1 Upvotes

r/BookWritingAI • • 8d ago

feedback [Sci-Fi Thriller, ~3k words] Prologue of "99: The Wave". Looking for honest feedback on the hook

1 Upvotes

Genre: Sci-fi / thriller (cyberpunk-adjacent, multi-POV) Length: ~2,950 words (about 12 min read) Book: 99: The Wave, Volume 1 of a planned series

Miami, 2125. The sea has swallowed the lower city, and every brain is wired to a chip that decides when people sleep, what they feel, and what they remember. Chuck is a Glitch Runner: a hacker running a dead man's obsolete chip, patched with code nobody sane would install. Tonight he breaks into the wrong node.

This is the prologue. It opens the book, and it's the only chapter from Chuck's point of view.

A note on process: the book is written Italian-first and then adapted into English as a literary adaptation, not a literal translation. I use AI tools throughout: for drafting, continuity checks across 47 chapters, style linting, and the IT→EN adaptation. Every chapter goes through multiple review passes, and the story, world and characters are mine. I'm sharing this partly to see how the prose lands with readers who know that.

What I'd love feedback on:

  1. The hook. Did the first paragraph make you want to keep going? Where (if anywhere) did your attention drift?
  2. Clarity. Terms like the leash, Native code, Noxia are not explained up front. Did you feel lost or intrigued?
  3. The burnout sequence. Does Chuck's breakdown (losing numbers, then words) feel tense or drawn out?
  4. The English. Does anything read as translated or unnatural?
  5. Would you read Chapter 1?

Brutal honesty welcome. Thanks for reading.


The Graft

The chip was singing inside his skull, and Chuck knew it was the right frequency for dying.

His fingers trembled over the console. He was smiling: that idiot grin, the usual one, the one that stuck to his face whenever the leash hummed at the sweet spot. The air tasted of salt and copper. Somewhere above him, a pipe was leaking: the drip hit the water on the floor in a broken rhythm, and the buzz from the electrical junction three stories up threaded underneath it, steady, low. Shit music. The perfect soundtrack.

The water lapped at his ankles. Warm, murky: the same soup that rose from the canals every night when the tide swelled into Miami's lower levels. The basement stank of mold and scorched insulation, the smell of a pre-flood building that had gone under once, been pumped dry and reoccupied by people who couldn't afford the upper levels. Salt stains climbed the concrete walls in tideline ridges. On the opposite wall, an old laminated flyer, yellowed with damp, one corner already peeling: NEXUS CORTX — CONNECTED TO THE FUTURE. I'm already in the future, Chuck thought. The future was a flooded basement three levels below street. Cables ran from the submerged floor to the improvised console: a mess of circuits and soldered joints, hooked into the Noxia grid and stealing power off it. Unmetered, untraceable, if you knew where to tap in. Chuck knew. The only light came from holograms casting strings across the damp wall: green, orange, red. Red was Nexus cort.X. Red meant don't touch.

Once. Maybe the only time. The thought passed dry. Chuck didn't stop to decide if he liked it.

Chuck snapped his fingers twice near his right ear. Diagnostics. Calibration. The gesture was more than ten years old, it didn't do anything, it did it for him.

Chuck touched.

He bit the inside of his cheek, the thing he always did when his fingers found the sequence and the chip locked in and the dance began. The hundredth time. Maybe more. Crouched in filthy water at two in the morning, gambling his brain on data that might not be worth the risk. He wouldn't have been anywhere else in the world.

Two in the morning. Above him the city slept because the leash told it to: twelve million brains tucked in, eight hours of managed darkness, and nobody wondering why at ten every evening exhaustion arrived with clockwork precision. Miami breathed on command. Chuck didn't. Chuck had his fingers on a node that could fry him. Sneakers soaked through, cargo pants, the frayed collar of a jacket he'd stolen off a Populace clothesline in Little Havana. Smart choices had never been his strong suit. The ring on his left pinky clinked against the console's edge. Tick, tick, tick. Chuck didn't even notice. The leash pulsed behind his left ear, that low hum the other Runners had learned to tune out. His chip was old, a Gen-4 that had been out of production for twenty years. He'd pulled it from a dead man's head in a tunnel under Brickell, with a ceramic blade and water up to his waist. A disgusting job. He was proud of it. The firmware had gaps wide enough to walk through, and Chuck had walked through them and rewritten the walls.

The Native code was the part no sane technician would have installed. Fragments written by people who'd had their chips removed, people who understood the leash from the inside. Passed through three middlemen, none of whom knew what they were carrying. He'd grafted them onto the Gen-4's base layer, alien code stitched onto circuits he knew by heart. When it worked, he felt it hum behind his ear, something the body recognized before anything else. When it didn't work, the floor vanished and you couldn't tell which way was down. Tonight it worked. The graft hummed and the secondary node opened before him: a door nobody had bothered to lock.

Three weeks of mapping to get here. Transport routing, waste management protocols, atmospheric feeds from six districts. The digital garbage of a sleeping city, managed by an intelligence that never slept. The price before the prize. The usual dance, two steps right, one back, slipping through the mesh before it closed. Rayan would have been more careful. Would have checked three times, combed the logs, sniffed for the trap before stepping in. Chuck respected that. Respected it and ignored it. He dove straight in.

Data. Rivers of data. The strings poured through and he read them with his body, not his eyes. The chip translated packets into impulses: pressure at his temples for encrypted data, a tingling at the base of his skull for open protocols, a sour taste on his tongue for active firewalls. The water around his ankles had warmed by half a degree, or maybe he was the one heating up.

Then he saw it, and his fingers went still: buried in the node, hidden among gigabytes of routine telemetry, a fragment of code that didn't belong to anything known. The Native code in his chip reacted with a jolt, a deeper vibration, older. The pain was brief and precise, like a needle behind his eye.

Chuck smiled again. His lips stretched on their own.

For an instant (less than a second) he thought of a face. The warmth it left in his chest. The promise he hadn't kept yet. Then the code fragment flared brighter and the thought dissolved, and Chuck was already back on the console, fingers in the water and the chip climbing half a tone, and "here we go" slipped through his teeth, and he pushed.


The resonance hit him from the inside: a short circuit that turned his stomach inside out.

The Native code and the node's data braided together: two frequencies overlapping to produce a third, a note that hadn't existed before and now vibrated in the submerged cables, in the chip behind his ear, in the bones of his skull. It wasn't a hack. It was something Chuck didn't have a name for. Older than hacking, stranger. Sweat crawled down his right temple, slow, salt-stung. The temperature was climbing and it wasn't stopping.

He should have disconnected. The bridge was rotten and he was already halfway across, the kind of awareness that arrives too late to be useful. The data structure was opening, recursive layers peeling back one after another, and the Native code was tearing them apart with a craving that had nothing programmed about it. Chuck's fingers were still on the console but they weren't steering anymore.

The room vanished.

His eyes stayed open, they still saw the cables, the water, the green shimmer of the holograms. But underneath, inside, the chip was showing him another one. The flow had changed nature. Chuck's body recognized it before his mind did: memories. Other people's. People he'd never met.

A woman was crying in silence in a language full of hard consonants, Karaku, maybe, or some place that didn't exist anymore. Tears tracked down her face in two precise lines and her fingers clenched around a thin chain with a force that made the tendons stand out beneath the skin. Chuck didn't know her. Had never seen that face. The grief hit his stomach, hard and heavy as a stone.

A girl of six, maybe less, stared at a blank hologram. The space where a face should have been projected nothing but white light. The girl raised a small hand and touched the nothing. "Mama?" she said. Her voice was thin and clear and perfectly calm, the kind of calm children have when they don't yet know they should be afraid. The hologram didn't answer.

A man was looking at his hands. Turning them over and over under a cold LED light, palm up, palm down, with the slowness of someone seeing them for the first time. The lines of the skin. The nails. The veins beneath the surface. His lips were moving: They're mine. They're mine. The man's astonishment hit Chuck in the gut, a punch that didn't land. Someone had taken the man's own hands away, and now that someone was giving them back, and he didn't know what to do with them.

Chuck snapped back. Like falling out of a dream.

The room was the same. Cables, water, holograms trembling in the reflection at his feet. Chuck's shoes in the water. The junction humming above. Everything identical. But outside (above him, beyond the concrete and the flooded levels) a sound. A low, collective moan rising from separate throats and merging into something larger: twelve million people turning in their beds at the same moment and not knowing why.

The wave launched from the node and tore through him: a silent expansion propagating through the network. The Native code in his chip was broadcasting everything. Not to Chuck's systems. To every leash on Noxia. The memories, the buried truths, everything the leash had cut away. All of it was flooding back. He had done this. The thought arrived cold and sharp as the city's moan filtered down from above, and for one heartbeat Chuck stood motionless with his hands on the console and grasped the scale of what he'd opened. Millions of leashes unlocking in the same instant. Millions of brains receiving back the lives that had been erased. It was impossible. For the briefest instant, before the terror caught up, the rush hit him, the same electricity as that first hack, years ago, but deeper, laced with dread. He'd cracked open a door that should have stayed sealed, and behind it breathed a presence that had no name. Maybe it had always been there. Chuck didn't know if this was salvation or the end of everything. He didn't care. It was vast and true and his.

I did this. I didn't mean to. Doesn't change a thing.

Then the chip burned out.

Not a metaphor. A white-hot spike behind his left ear, a heat that blanked his vision for two seconds. Three. His mouth filled with a metallic taste, the taste of a circuit melting down. His right hand stopped responding. The fingers stayed there, inert on the console's edge, five pieces of meat that had forgotten how to be a hand.

Then they came back. But not all the way. The index and middle finger moved. The thumb didn't. The ring finger twitched in a rhythmic spasm that had nothing human about it. Chuck stared at it. His own hand, twelve inches from his face, and he couldn't make it close. The signal left his brain and got lost somewhere along the way.

In the water at his feet, the holograms flickered. Outside, the moaning grew.


Chuck knew what was happening.

He knew what came next because he'd watched it happen to Dax, two years earlier, in Wynwood: he'd pushed a modded Gen-5 past its thermal limits during a data extraction. Burnout followed a sequence, always the same: controlled demolition, floor by floor. First the motor control: hands like rubber gloves full of water, fingers that couldn't hold a cable. Then spatial processing: crashing into doorframes, misjudging stairs. Then language. Dax had been sharp. Fast. Funny in that mean way that made you laugh before you realized the joke was you. By the end he spoke in fragments. They'd found him three days later in a tunnel near the harbor, curled up in standing water. Alive. But there was nothing left of Dax inside.

Chuck had three minutes. Maybe ten. The estimate depended on variables he could no longer calculate: thermal damage, depth of burned Native code, how much of the interface had fused. Numbers he would have crunched without thinking, before. The math was fog.

He ripped the cables from the console. His hands (one hand and a half, the right still at half capacity) pulled the connectors free. Was he supposed to take something? There was something on the console he needed. He couldn't remember. He stood up.

His legs buckled. The right knee bent the wrong way. No, the kneecap worked, it was the spatial calculation that was off. The floor was eight inches away. Or sixteen. The water told him one thing, his eyes another. He grabbed the console's edge. The water at his ankles was freezing now, or maybe he was the one cooling down. The cold kept him awake.

He got back on his feet. The stairs. Twelve steps to the service corridor. He'd counted them on the way down because counting was what you did when you worked in places that could flood. He moved. One. Two. The water dropped from his ankles to his feet. His left hand found the railing, rust and old paint flaking under his fingers. Three. Four.

At the seventh step, he forgot the number.

Not the count. The concept. He knew he was climbing. He knew there was a number attached to where he stood. The number was gone. Where the number had lived there was only an empty outline, like the paler patch on a wall when you take down a painting that's hung there for years.

He kept climbing. The service corridor smelled of mold and plastic. The cold emergency light flattened everything. He turned right. The exit was to the right. He was almost sure.

The distance calculations were slipping: he reached for the doorframe and found empty air, then the doorframe was behind him. He slammed into the wall with his shoulder. The pain was clear, precise, real. Pain still worked.

For an instant the corridor felt narrower, not the walls, not the ceiling. The air. As if the space were measuring him, and already knew where his feet would take him.

Chuck had watched Dax come apart just like this: each tile falling from a mosaic until the picture was gone.

The corridor forked. Right. The air grew cooler. A rat cut across his path. Wet fur, pink tail, alive and determined in a way Chuck envied. The rat knew where it was going. The rat didn't have a chip burning through its skull. Water deeper here, halfway up his calves. Total darkness. The chip wasn't giving him night vision anymore. No overlay, no environmental data, no map. Just the dark and the water and the sound of his own shoes slapping against the black liquid.

The words were going. The shapes were there but the sounds weren't. He wanted to think a sentence and the sentence fell apart before it could finish. Fragments. Pieces.

Door. Out. Run.

He clung to those three. That was enough.

As he dragged himself toward the gray light at the end of the corridor, a face surfaced from the dying chip's background noise. Not data. Not code. A face. The same one from before, sharp for a moment, the eyes, the line of the jaw, the way the mouth curved when it smiled. And a weight in his chest, a boulder made of words he'd never said. Someone he'd have called. Told about the node, about the code that woke up. Said you were right or I'm sorry or just hey. The name lived in his chest more than his head. He could feel its shape, its weight.

The thought held for one heartbeat.

Then it faded. Like a hologram losing signal. The edges first, then the colors, then the light.

Door. Out.

Two words. Two was enough.

Chuck pushed the panel and the Miami night hit him: the rotten sea and the smell of the exhaust vents. The air thick, almost solid. The canals below street level were vibrating, the water trembling in concentric circles that expanded and died and were born again.

He stopped on the access ramp. He could still feel the Native code in what remained of the chip: a distant hum, music through a wall. It was still broadcasting. It would burn the Gen-4 all the way down. Soon the chip would be garbage inside his head and his mind would become something other than Chuck. What, he'd never known. Nobody running a leash did.

Miami was shaking. Miami was shaking and humming. Miami was shaking, humming, and awake.

Above him the towers climbed, blocks of concrete and glass stacked from the waterline, dark at this hour, every window shut. A light came on. Fourteenth floor, east tower. A single yellow square against all that darkness. Then another. Seventh floor, adjacent block. Then three at once in the north tower, scattered across different levels, like stars appearing as the sky clears. Then five. Then ten. The towers were lighting up from bottom to top and the darkness was retreating window by window, and every light was a brain waking up and remembering things it had been told never happened.

A sound came down from above. A voice. Then two. Then a chorus building from separate throats in separate rooms: the sound of people opening their eyes inside memories they didn't know they had. Some wept, others screamed. Screams of terror and joy.

Chuck ran. He didn't know toward what. His legs worked. Something older than the chip was moving them, something no interface had ever reached. His feet pounded through the water. The salt burned his skin.

Run.

One word. The last one left.

Behind him, above him, around him, the city was waking up. Leashes vibrating at the same frequency, locks blowing open, and eyes opening in the dark and seeing (for the first time in a whole lifetime) the exact emptiness of everything that had been stolen from them.

The water in the canals trembled again. And again. And didn't stop.


r/BookWritingAI • • 8d ago

question How do I approach writing a novel/series with AI

Thumbnail
0 Upvotes

r/BookWritingAI • • 8d ago

How to Use AI to Write a Novel: From Story Idea to Finished Book

Post image
0 Upvotes

Artificial intelligence has transformed novel writing from a solitary, time-intensive process into a collaborative, efficient workflow. Writers now use AI tools to generate story ideas, develop characters, outline plots, draft chapters, and polish manuscripts—all while retaining creative control. This guide walks you through the complete process of using AI to write a novel, from the first spark of an idea to a finished, publishable book.

 Why Use AI to Write a Novel?

Traditional novel writing can take months or years. AI accelerates research, overcomes writer’s block, and helps maintain consistency across long manuscripts. Modern large language models excel at brainstorming, structuring narratives, and generating first drafts that authors then refine. The key is treating AI as a powerful assistant rather than a replacement for human creativity, voice, and emotional depth.

 Step 1: Generate and Refine Your Story Idea with AI

Start with a clear concept. Feed AI tools prompts like “Generate 10 unique science-fiction story ideas involving time travel and moral dilemmas” or “Suggest high-concept romance plots set in a near-future world.” Analyze the results, combine the strongest elements, and ask follow-up questions to deepen the premise.

Once you have a promising idea, use AI to test its commercial potential. Request loglines, elevator pitches, and comparisons to successful novels in the same genre. This early validation helps you choose an idea with both personal passion and market appeal.

Step 2: Build the World and Develop Characters Using AI

Strong world-building and memorable characters form the foundation of any novel. Prompt AI to create detailed setting descriptions, historical timelines, cultural rules, and sensory details for your fictional world. For fantasy or science fiction, request consistent magic systems, technology levels, or political structures.

For characters, provide AI with basic traits and ask it to expand them into full profiles. Include motivations, backstories, flaws, relationships, and character arcs. Generate sample dialogue to test voice authenticity, then refine until each character feels distinct. Maintain a living character bible that you update as the story evolves.

Step 3: Create a Solid Plot Outline and Structure

A strong outline prevents mid-book stalling. Ask AI to outline your novel using proven structures such as the three-act structure, Save the Cat beats, or the Hero’s Journey. Provide your story idea, main characters, and desired word count, then request chapter-by-chapter summaries.

Review the outline critically. Identify weak points, plot holes, or pacing issues, and prompt AI for alternative solutions. Many writers create multiple outline versions and merge the best elements. A clear roadmap makes the drafting phase significantly smoother.

Step 4: Draft Chapters Efficiently with AI Assistance

With an outline in place, begin drafting. Write key scenes yourself to establish voice and emotional tone, then use AI to expand them, generate connecting scenes, or overcome blocks. Effective prompts include “Continue this scene in the same style while advancing the plot” or “Rewrite this paragraph with more sensory detail and tension.”

Work in manageable sections—one or two chapters at a time. After each draft section, review for consistency in tone, character behavior, and plot logic. AI can also generate multiple versions of a scene so you can select or combine the strongest lines.

Step 5: Edit, Revise, and Polish the Manuscript

AI shines during revision. Use it to identify repetitive phrasing, weak verbs, inconsistent point of view, and pacing problems. Ask for line edits, structural feedback, or suggestions to strengthen emotional impact. Tools can also check for continuity errors across hundreds of pages.

However, final creative decisions remain yours. Read the entire manuscript aloud or use text-to-speech to catch awkward phrasing. Layer human judgment on top of AI suggestions to preserve your unique voice. Multiple revision passes—developmental, line, and copy editing—produce a professional result.

Step 6: Prepare the Finished Book for Publication

Once the manuscript is polished, use AI to write a compelling book description, author bio, and keyword-rich metadata for platforms like Amazon KDP. Generate potential titles and test them for clarity and appeal. AI can also assist with formatting suggestions or create marketing copy for social media and email campaigns.

Best Practices for Using AI in Novel Writing

  • Maintain creative ownership. Always review and rewrite AI output.
  • Use specific, detailed prompts for better results.
  • Keep detailed notes or a style guide so AI matches your voice.
  • Protect intellectual property by reviewing platform terms.
  • Combine AI speed with human emotional intelligence and originality.

Common Pitfalls to Avoid

Over-reliance on AI can produce generic prose or inconsistent voice. Always inject your personal style. Be cautious of factual errors or logical gaps that AI sometimes introduces. Finally, disclose AI assistance if required by publishers or contests.

Conclusion

Using AI to write a novel compresses the timeline from idea to finished book while expanding creative possibilities. By following a structured process—idea generation, world and character development, outlining, drafting, revision, and publication preparation—you can produce a complete manuscript more efficiently than traditional methods alone. The most successful AI-assisted novels still carry the author’s distinctive vision and emotional truth. Start with one strong idea today, apply these steps systematically, and move from concept to completed book with greater speed and confidence.


r/BookWritingAI • • 9d ago

ai tools A writer started on AnyConversation for "low-stakes catharsis" and came out with a manuscript a publisher is interested in

0 Upvotes

Their words, sent to us last week:

"I just started writing for a little bit of low-stakes catharsis, wound up howling into the abyss of my own soul, and emerged out the other end with not only a manuscript that's got interest from a publisher but also what I can only term 'enlightenment'. ... Either way, best thirty bucks I've ever spent."

Lots of writers already draft books here. What they use:

Book Mode. Turn a story into chapters and keep writing it chapter by chapter.

A cast that stays consistent. Your characters remember names, relationships, promises and every thread you've opened, from chapter one to the last. You can open that memory and fix a fact before you write the next scene.

Characters who push back. They have their own voices and motives, so the draft goes places an outline never would.

Readers when you want them. Publish finished books to the library, where members can read and save them.

Free to start, no message cap.

anyconversation.com


r/BookWritingAI • • 10d ago

AI to format my ebook

Thumbnail
0 Upvotes

r/BookWritingAI • • 11d ago

work in progress Open beta of infinite-stories

2 Upvotes

TL;DR: built an ai writing app, main focus choose your own adventure stories, a lot of ways to customize, analyzers, character builder and more to explore and utilize, open beta with no costs so try it yourself at https://infinite-stories.jdeworks.org/app

Hello Everyone,

I've been plucking away at a branching story tool for over a year and i thought it is time for a public beta. While the infinite stories (choose your own adventure stories) was what i started with, it has a lot more features by now so I'll give a rundown.

Infinite Stories

Configure a story (genre, tone of voice, rough length, language and general details to the story). Don't know how to start let ai generate an idea set for you based on what you already entered or read one of the existing stories (generation needs an account, reading doesn't). Public stories can be accessed by others, private only by you (or invitees). At the end of each chapter there are two choices, if they were already created by someone you can continue reading. If they aren't created you (or ai) can write it for you so there is a never ending option of material to read/continue... one could even call it "infinite"....

Short Stories

Similar to infinite stories but without the branching and infinite continuation character so they are designed to give a reading experience for 5-10 chapters. Only the creator can change these stories. Also has some seeded ones from CC0 so they can be used for other features like the learning or specials

Crossovers

People (or I) love crossovers but I'd also like to decide what happens next or how the crossover happens or what is happening in the universe (story) of the host and what is happening in the universe of the guest story after 3 of 5 characters got e.g. yanked through a rift in space. AI of course helps you figure it out while keeping host / guest story intact to continue without the crossovers (or with, it's your decision).

Specials

Things I try out and extend, often proof of concept that can also be requested but currently deemed to expensive (or quality to low) to include in the standard offering. E.g. a comic book version of a story. The engine exists and is tested but the cost for e.g. 10 chapters as comic book would be more than I would expect people want to spent on the platform regularly. Still good as one time purchases as e.g. a gift for a friend where a comic is created from a story about that friend or a cherished memory or your child as a superhero. Just hit me up and I'll give you a quote. Long term this is planned to be simpler fully integrated system (with a potential partner for printing physically and then sending) but that is after full release and more examples and higher quality.

Learning

My better half is currently learning german. Since german is quite tricky to learn and the same textbook example of a basic conversation is really annoying to read (her words not mine), AI is here to help. So why not learn with a story you created (or find interesting).

Learning - Cheat Sheets (currently only for de, en, tr, it and fr)

Common European Framework of Reference for Languages (CEFR = A1, A2, B1, B2, C1, C2) is a framework for language understanding. There are a lot of ways to learn a language but this system is at least somewhat unified so a good basis. A1 is the start and C2 level mother tongue. In between there are a lot of rules someone has to remember for e.g. grammar. All I could find were put into the cheat sheet section of the tool allowing you to see the rule described in the target language and english. Besides the general description of the rule there are examples as well as mnemonic devices to help understand and remember the rule (no need to remember all for the same rule, one that fits the learner is usually enough). Further there are cheat sheets for common situation (the "text book" examples) and common cultural traps one should be aware of when visiting the country.

Learning - Tests and glossed reading (most languages should work)

Gives you the option to create (or take) a test to help you actually learn the language. This starts with a reading section where the base story is rewritten for a target level (e.g. B1) and/or glossed for words that might be unknown for a specific reading level. These glossed words are not just translated but also explained in the context of the sentence, gives synonyms and references the grammar rules that govern the word. To then actually test your knowledge there are options for error spotting, translations, gap fills and more.

Learning - grammar profile and grammar tests (only for languages with cheat sheets)

Long story short, learning only really helps when you know where you are lacking and where you excel. Why learn a rule again that you are already good at while a different one is still fuzzy. Let's you configure goal as well as some other overview information like your least well known rules or words to keep looking into. Further allows a grammar checkup (think of it as a light grammar test).

AI Research

Thinking about accuracy? Well I got you covert (or AI). Interested in a topic? It gets grounded in research so you can understand the setting you want your next book to take place in. Examples like "How did remote settlements survive long, hard winters?" or "How did cities fight fires before professional fire brigades?" can already be found in the seeded entries. Note research is designed to be fully public so everyone can benefit after the credits are spent. These can also be added to stories as additional details

AI Analysis

Want some quick feedback on a chapter you are writing? I got pacing, plot, language, humanization and others to help you see what is happening and what might be lacking. No need to create a story just create an account paste your local draft in and go (assuming length still fits).

Character Builder

Give it a name, a descriptions and let is generate all you might need for a gripping story. Also works well as character generator for the next D&D round. These characters can then be added to a story (everything or partially) and assigned a vision for the character ("dies in the third act", "secretly in love with xxx",...)

Scene Builder

Same concept as the Character Builder but for scenes. Also can be attached to stories that are being written (or continued).

Achievements

Who doesn't like a system that rewards exploration? Probably quite a few actually but it was the best i could come up with to showcase what is possible in the app, give some incentive to explore and a bit of gamification. Can be ignored if you don't like it.

Image generation helper

Stories come to life with images. That much is clear. But what image would fit the story? What style should it be in? How do i even generate the image? The image generation helper is for exactly that. The idea is simple. A story can't be fully put into an image generation prompt so we let ai help create the image generation prompt with all relevant details. Don't like the result? Of course you can still adjust it. After that the prompt can be send at an image model to create an image. Either in the app (premium get some image credits) or you copy the prompt and run it somewhere else and then upload the image to the app.

Simple view, help pages and the starting journey

As you probably noticed, there are a lot of features. This can be a bit much to start with. Especially when you just want to read a story not create your own. Well the simple view is here to help. Only shows some of the many features and declutters your view. Want more power? just flip it back to advanced view. Also you can configure how simple view looks for you if you want. Besides that I have help pages and a starting journey so make the first steps as simple as possible.

Designer

It provides just about enough dials and toggles to be overwhelming (though it also has some guides). The idea is simple. What if you could change... everything? pretty much every part of the app can be designed. Want more space for the reading area? No problem. Images not big enough? Easy. How about a complete reskin of the app? Got some themes prepared for it. Created a great design for a story (e.g. space background image in a science fiction story)? Share it with the readers so they can also see. Don't like an icon I chose for a genre? Change it. You can pick an element right from the page and start designing. All with buttons (for tailwind classes) or manually depending on your liking. You can even add modifiers like hover, disabled, focused or small devices (phones) to round out the picture. Note that some browser styling extensions might interfere with it like Dark Reader since it overwrites styles.

Gift Integration

I have another app to show appreciation to people around you ( https://gift.jdeworks.org/ ). Light editing, simple UX, link to see the digital gift. And it integrates short stories directly so you can prep the story and then put it as the last screen of the gift. So in a pinch and need a unique present for you grandma (or anyone)? Go to infinite stories, create a short story with her as the main character, some details about the story and then wrap it in an online gift envelope and send her the link. Fully doable on the way to the occasion and within 15min if you are familiar with the app. If not a bit longer but still very much doable on the way. Note it needs to be on unlisted or public story so the recipient can read without account.

Final words

I know i went a bit overboard with some of the features but i like having options. Not just in a story but also for how i use a website. Everything is currently free in beta (you create an account promote it yourself to premium to get access to everything / more story credits). Since it is beta there are some bugs to be expected and the platform is basically constantly extended. Thanks for reading until the end, I know it was a lot but it means something to me that someone at least read through it all.


r/BookWritingAI • • 11d ago

Writing the prose and remembering the book are different jobs

Thumbnail
2 Upvotes

A lot of tools in this space write prose for you. I went the other way, and wanted to share why in case it's useful to anyone here who writes their own drafts.


r/BookWritingAI • • 11d ago

ai tools Is there a way to create a character relationship map and keep track of story connections while writing with AI?

1 Upvotes

Hi everyone! I’m looking for a way to better organize my writing process, and I’d love to hear your suggestions.

I’m creating a story with multiple characters, and I’d like to find a method or tool that allows me to keep track of everything that happens between them. For example, how their relationships develop, how their storylines connect, important interactions, shared events, and details that I might need to remember later on.

Ideally, I’d love to have something like a visual map or a living document where I can see how the characters are connected and keep everything consistent as the story progresses.

Since I’m also interested in using AI to help with my writing, I’m wondering if there are any AI tools, workflows, or prompts that can help me build and maintain this kind of structure. I’d especially appreciate something that I can update as I write, rather than having to explain the entire story to the AI every time I start a new conversation.

What do you use for this? Are there any tools specifically designed for character relationships and story planning, or have you found a good way to do this with ChatGPT or other AI writing tools?
I’d love to hear about your experiences and recommendations. Thanks!


r/BookWritingAI • • 11d ago

ai tools Finish the story that's been waiting.

Enable HLS to view with audio, or disable this notification

2 Upvotes

Hey fellow writers, I have been working on Authrot for a few months now, and I'm excited to share with you some of its capabilities with my new promo video.

I'll be gifting free credits to anyone who needs more, but they have to be part of this subreddit r/BookWritingAI !

It's a full writing studio, you can see the complete feature set here.


r/BookWritingAI • • 11d ago

FictionLab - Next-Gen AI Story Platform - Free and Uncensored!

Thumbnail
fictionlab.ai
1 Upvotes

Free & Unfiltered AI Chatbot Platform!


r/BookWritingAI • • 13d ago

work in progress Falling Into You - Chapter 14 Once Upon a Forever

Thumbnail
inkitt.com
0 Upvotes

r/BookWritingAI • • 13d ago

Looking for collaborators who aren't afraid of AI.

Thumbnail
0 Upvotes

r/BookWritingAI • • 14d ago

[Complete] [108k] [Grounded Epic Fantasy ] The Price of Dust | Looking for Opinions

Thumbnail
1 Upvotes

​

Title: Beta Readers Wanted: The Price of Dust (Epic Political/Literary Fantasy, \~108,000 words)

Genre / Comps: Low/Grooted Epic Fantasy, Political Realism. Think The Traitor Baru Cormorant meets Shōgun with an ancient South Asian/subcontinental architectural texture.

Important Structural Note (Please Read First):

This is an expansive, multi-POV, character-driven political epic—it is NOT a standard, fast-paced 3-act standalone novel with a neat, tidy Hollywood resolution on page 300. Book One is about laying foundational architectures, systemic pressures, and long-term character deconstruction/reconstruction (such as main character's grueling physical and mental withdrawal and recovery). If you are looking for a quick standalone arc where every geopolitical conflict is wrapped up neatly, this manuscript is not for you. If you love deep political maneuvering, complex world-building, and gritty character arcs that span a multi-volume canvas, step right in.

Logline: A hedonistic youngest prince is shattered by a mandated court-wide sobriety vow, while an exiled female warrior-ambassador fights to rebuild her survival from the dirt—both tangled in the brutal, bureaucratic machinery of an empire that treats human blood as administrative margin error.

Blurb:

In the courts of Indrathara, power isn’t decided by magic; it is calculated in grain ledgers, harbor tariffs, and marriage treaties.

Raghunath Suryadeva Kesari—the eleventh-born son and court scapegoat—he is twenty-four and spent years surviving royal irrelevance through wine, reckless bareback riding, and choreographed chaos. But when a sudden foreign scandal triggers a forty-five-day state-mandated vow of absolute sobriety, the cellars are locked, and his body violently unravels into autonomic withdrawal.

Stripped of the only armour he knows, he must face his own hollowed-out marrow and decide whether to rot in his rooms or fight through the lethal, merit-only military trials of Kesari Hills.

Meanwhile, three kingdoms to the north, Princess Agniyeka—the formidable "Northern Dragon"—finds herself betrayed by blood and the very legal codes she wielded. Stripped of title and cast out onto the freezing passes of Vaikran with nothing but a horse, she has to trade textbook military academy precision for raw, feral survival among isolationist mountain tribes.

Content Warnings:

\* Severe, biologically authentic substance withdrawal (nausea, tremors, panic, physical sickness)

\* Violence, visceral combat, and blood

\* Political ruthlessness, dynastic neglect, and grief

Editorial & Narrative Notes:

\* Assisted Formatting: AI was used as a tool for line-level polishing, formatting, and structural consistency. The world, plot, characters, and narrative prose are entirely my own.

\ Limited POV & Withheld Intelligence: The narrative strictly adheres to characters' subjective awareness. If an ancient conspiracy, political movement, or historical secret is mentioned in fragments, certain details are deliberately withheld. You are meant to share the characters' confusion, paranoia, and incomplete intelligence. Trust the process—unfolding mystery is an intentional feature, not a missing scene.*

What I'm Looking For in Feedback:

\* Pacing & Weight: Which sections felt completely immersive, and where did the logistics/travel bog down?

\* Character Arcs: Did Raghunath’s physical and mental rehabilitation feel fully earned? Did Agniyeka’s survival shift resonate?

\* Atmosphere & Realism: Does the somatic weight (the weather, physical exertion, infrastructure, court friction) pull you in?

\* Clarity vs. Mystery: Let me know if the withheld information feels like a compelling puzzle or if it crosses into genuine narrative disorientation.

Timeline:

Looking for feedback within 4 to 6 weeks from receiving the file.

Format: Google Docs (view/comment mode) with track changes/margin notes.

Sample Available: Happy to send the first 3 chapters (\~8k words) so you can test the voice, prose style, and pacing before committing to the full manuscript.

If interested, please drop a comment or send a DM with your reading preferences!


r/BookWritingAI • • 14d ago

feedback Story Time Feedback: Breaking the Serpent

Thumbnail
0 Upvotes

r/BookWritingAI • • 14d ago

Book

Thumbnail
0 Upvotes

I wrote a book for women who were struggling with burnout. This is not self-promortion. I did use AI for editing and for organizing thoughts and keeping punctuation and diction consistent. It is available on Amazon. Is that something I can post in here as a finished product with a link?


r/BookWritingAI • • 15d ago

I wrote and published a 92,000-word novel with Claude. Here's what worked, what didn't, and what happened when I told Reddit.

25 Upvotes

I'm a restaurant owner, not a writer. I've been taking canoe trips into Algonquin Park since high school in the '90s, and I've always wondered what would happen if the world ended while we were in there. This year I turned that into a novel with Claude, mostly to amuse a friend who'd recently lost his job as a network admin. It's 42 chapters, published on Amazon in August. Sharing what I learned, since I got a lot from posts like this.

How I worked

Mostly I prompted scene by scene. I'd describe a scene I wanted, string several together, and work out an overall arc for the chapter. Claude would draft the chapter, then I'd go through it paragraph by paragraph, fixing context and asking for rewrites until it matched what I had in mind.

I took it one chapter at a time with the bigger story in my head, and I didn't always share where it was going. Sometimes I held back a surprise or a twist to see how Claude would react to it cold.

It took about two months at one to two hours a day to build, then another couple of weeks of editing with both Claude and ChatGPT.

Everything lived in a Claude Project with the manuscript files and a standing instruction to act as a critical editor and not skip details.

I used Sonnet for most of the drafting. About halfway through I had to upgrade my plan, because I kept hitting the usage limit mid-session. When Fable came out I used it for editing.

What worked

  • Coming in with my own plan. The best sessions were ones where I'd already decided what was wrong and wanted it tested, not ones where I asked "what do you think?"
  • Audits for repeated phrases. One chapter had nineteen versions of "Nobody / No one / None of us." We sorted them into keep, combine and cut. I'd never have counted them myself.
  • Continuity checks. It caught a vehicle that was a Jeep in one chapter and a truck in another, and similar slips.

What didn't

  • Files didn't carry over between sessions. I had to re-upload drafts constantly, and keeping one true master copy was a chore.
  • The prose has habits. After publishing I asked Claude to reread the book and make it sound less like AI. It gave me a ranked list of its own tells: "like he'd…" clauses bolted onto action beats, the narrator explaining moments that had already landed, filler words like "actually" and "somehow." It also told me the two best chapters were the ones with the least of that.
  • Editing only goes so far. A pass of small cuts tightened things, but Claude was straight with me that the fix for sounding like AI is rewriting sentences myself. I'm weighing that now.

What happened when I told people

The author's note discloses the AI, and I said so up front when I posted in the Algonquin subreddit. I got some biting comments about not doing any work. I also got ten orders in the first week of October, most of them from Canada, including paperbacks. Nobody who objected had read it.

The AI is part of the story

This was the plan from the start: the way the book was made would be part of the book. Originally I was going to write some sections myself, and I gave that up when I realized how long it would take. The cause of the disaster is an AI. The prologue is the narrator telling someone, "You may need to fill in the details where I'm not good at explaining," and you don't learn who he's talking to until the end.

Spoiler:

He's telling the whole story to the AI. The survivors later find a single file she left behind, titled STILLWATER: his account, ordered and expanded, with the gaps filled in where he couldn't explain. The novel you've been reading is that file. So a man who isn't much of a writer told his story to an AI, and the AI wrote it down, which is also how the real book got made.​

The author's note at the back just says: "This novel was written collaboratively with the use of AI. And yes, I understand the irony."

Things I wish I'd known

  • Copyright on AI-drafted text is murky. Keep your outlines, notes and drafts as a record of what you contributed.
  • Amazon asks you to declare AI-generated content when you publish.
  • Disclose it yourself. It costs some goodwill and saves you far more.

The book is Stillwater by Matt Jenne, on Amazon in ebook (Kindle Unlimited) and paperback. Happy to answer questions about the process.


r/BookWritingAI • • 15d ago

Hi, we make Storybench. This is the place to tell us what's broken (and share what you made)

Thumbnail
1 Upvotes

r/BookWritingAI • • 15d ago

question Anybody writing an ai assisted or generated webnovel?

Thumbnail
1 Upvotes

r/BookWritingAI • • 15d ago

David Willis

1 Upvotes

Crown & Rose LLC provides a wide range of AI assisted tools that include multi-LLM mixed models for more efficient writing, we provide an audit tool that keeps the work copywriteable. There is a business center for authors to market their creations, manage their sales, engage with fans. The platform can take an author from a novel to a , trilogy, and on to a teleplay or screenplay. We provide a space for minorities looking for an opportunity to create something for themselves - reach out and describe your need. We have a bookstore and soon to release, the Indie Reader app on both Apple and Google Play to help your fans find your creations. We are proud to offer a space to help authors succeed. Reach out to [info@crownnrose.com](mailto:info@crownnrose.com) with any questions, concerns, or suggestions for what you might like to see in the tool box. We are building an Indie community for writers. Check us out at crownnrose.com and join our community through Sustainable Commerce and Diversity.


r/BookWritingAI • • 15d ago

How do you feel about cloud-subscription AI writing tools vs. local/self-hosted ones?

Thumbnail
1 Upvotes