Skip navigation
Currently Being Moderated

File Complexity/Size Maintenance; Paths vs Compund Objects

Sep 19, 2013 1:19 PM

Tags: #save #path #stroke #filesize

I have found myself using different methods to make designs, but I was wondering what was the best practice for archiving FINISHED products.


In terms of anchor and path complexity: would it be best to save files as paths with width controls, or should I be outlining strokes and flattening as compound objects?


If it turns out that the results would vary with every project, then I can accept saving two versions and deleting whichever happens to be the bigger file.

  • Currently Being Moderated
    Sep 19, 2013 2:41 PM   in reply to Puzmen



    FINISHED products


    And you believe in that concept?


    You should always keep a copy of the fully editable version before it(s continued development prospect) is destroyed.

    Mark as:
  • Currently Being Moderated
    Sep 20, 2013 7:22 AM   in reply to Puzmen



    let's pretend I have a client


    What about a separate PDF for that, either saved without AI editing capabilities or printed to PDF, for smallest possible file size?

    Mark as:
  • Currently Being Moderated
    Sep 20, 2013 3:32 PM   in reply to Puzmen



    I believe the saving option Smallest File Size is about as good (small) as it gets.


    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points