Skip to main content
Typothalamus
Known Participant
January 20, 2025
Question

Whether to continue with separate files or consolidate in one ID file as a rebuilt book

  • January 20, 2025
  • 3 replies
  • 1334 views

Over many, many months, it has driven me somewhat mad to have a current book divided into 47 separate chapter files, along with 10 additional files for front and back matter. This division has hindered the curation of illustrations and design elements, as I would have benefited from viewing and considering the work as a whole. It would've allowed me to make or eliminate choices more effectively while working on the entire project. I understand the purpose of InDesign’s Book feature, but it hasn't been ideal for my needs, given a strong preference to see everything in context and make sweeping changes as necessary. This fragmentation truly slowed progress. Now, however, all design and editorial decisions are finally locked in, and I find myself contemplating whether to continue with these separate files or consolidate them into one InDesign file, rather than a PDF.

Why?

Initially, I started with just such a massive file containing all the chapters, but after over thousands of iterartions, it suddenly, eventually, suffered some corruption, necessitating the split into smaller components to recover and avoid further issues. It became apparent the 'Save As' function should’ve been used instead of merely saving. But unfortunately, it was too late then, and the new fragmentation came at the cost of maintaining an easy overview. Reassembling the book using the Book feature has not been enjoyable or appropirate it seems; it complicates pagination and introduces numerous other problems I’d rather avoid. Yet, here I am. I suspect I’d prefer the entire book to be a single file, assuming ID can handle it – about 400 pp. (200 spreads), with ~200 illustrations and anchored side notes instead of footnotes/endnotes.

I recognize forum members will rightly view this strictly from the perspective of seasoned ID professionals and question the approach. As an editor first and a designer with a more manual and intuitive style, I haven’t engaged with ID at the level that might've been ideal. I hope for some understanding, but for our current purposes, it’s about clarifying strategies for moving forward in ID for this book, where my primary role to date had been to conceptualize, edit, and manage.

For now, I have two main goals to address:

  1. How can I best consolidate everything into one file if not with the Book feature, and can ID actually handle 200 spreads in a single file?

2. The significant task of rebuilding. Although I initially attempted to establish line measures, styles, alignments, column gutters, grid, and, most importantly, key content, at the start, it took considerable time to actually finalize. It simply evolved, contingent on many factors and myriad interrelated issues arose, some of which couldn’t be resolved as I progressed through chapter after chapter, developing editor’s notes, illustration choices, and design elements. It is a complex work of architecural theory, now annotated and illustrated. While the document may appear visually pleasing today, it is, underneath, a tangled mess of minor inconsistencies and manual adjustments. It's why I’m contemplating the major task of rebuilding. If I do, it must be done right this time (now that the harder creative and editorial work is done). Perhaps I'm not the one to do it, but after so much, I feel it is possibly the final hurdle. If I am to do it, then new threads  may cover some specific details.

Apologies for the length. A long road, circuitous, with poor process, but I do not question the end effect now in the final product. The book's impact and explications are miles above the poor process.


3 replies

James Gifford—NitroPress
Legend
January 20, 2025

There are, in the end, only two reasons to use a Book structure —

  • If the chapters, or overall project, is extremely large and breaking it into pieces makes editing, file management, crash recovery etc. easier.
  • If the chapters need a lot of individual editing, composition, development etc., especially by more than one person. If chapters need an author, a technical reviewer or editor, and then the designer to work in concert, separate chapters greatly simplify this piecemeal work.

 

But other than that, novices (and even experienced users doing their first large book) often overestimate the problems of large chapters and go with a Book format when it's not really needed. And many newcomers assume that the Book structure is necessary, or useful or good in and of itself, when it brings little to most one-author/designer projects.

 

It is quite easy to manage even relatively large books as a single file, using features such as Parent pages, sections, and paragraph styles. Books often bring all kinds of complications and headaches that are greater than any advantage. It does take some experience to make the correct judgment.

Robert at ID-Tasker
Legend
January 20, 2025

@James Gifford—NitroPress

 

There is one more rreason:

  • When the same file can / should be used in multiple publications in the same form - and / or on its own 

 

James Gifford—NitroPress
Legend
January 20, 2025

That too; shuffling standard components into different end publications. Funny I always forget that one when I've used it any number of times for complex documentation projects.

 

I could caveat myself by suggesting it's not really a common practice for most authors/novices and is only used in more... industrial/commercial settings. But that would be cheating. 🙂

Robert at ID-Tasker
Legend
January 20, 2025

@Typothalamus

 

If you need help in analysing your document - I can give you access to the full version of my ID-Tasker tool for free.

 

What kind of pagination problems do you experience? 

 

Typothalamus
Known Participant
January 21, 2025

With the Book feature, it was an overlap of page numbers, or not numbering, or not numbering quite correctly in some other way – a tricky issue when the page numbers in this book are also, too a degree, more designed in placement and styling, than a basic U-Haul book job. I wish to steer clear of ID taking too much control of this.

But now, with the answers from the forum here, I see that the Book Feature is often somehow over-emphasized and not suited here, to me, so assembling to pdf with it is now jettisoned in favor of a single large ID file.

With the myriad little inconsistencies to my files, tool analysis, as you've shown, should help. 

Peter Spier
Community Expert
Community Expert
January 20, 2025

At this point I would say this is really a personal choice. You already know the dangers (and potential slowdowns) of working with very large files, but what suits you and your style of work is the important factor here, as long as you take the required precaustions anuse best practices.

 

Combining into a single file is really not a big deal.  Make a copy of the first file and save with a new name, then open it and the other files (one at a time to avoid confusion), select all pages in the second file and from the Pages Panel flyout menu choose Move Pages and choose the copied first file as the destination. Do a Save As and now you have both a cobined version and the individual files for backup.

Typothalamus
Known Participant
January 20, 2025

Peter, thank you. For now, can I be assured that InDesign can manage a 400-page art book in a single file?

Peter Spier
Community Expert
Community Expert
January 20, 2025

I think the question is more can your system resources handle it.

And which version of inDesign are you using? I'm a little nervous about the bugginess of the latest versions.

That said, it's easy to make the single file, not terribly time consuming, and can be done without risk to your existing files, so it's worth trying.