Illustrator CC 2014 - save for web cuts off image

In Illustrator CC 2014 when I save a vector image with a thick stroke (e.g. 20pt) while using save for web and clipping to the image (so not selecting clip to artboard) and scaling to e.g. 20%, then the edges of the drawing are cut off.
I'm not completely sure but I think previous versions didn't have this issue.
If I save the image at 100% no edges are cut off.
I suppose save for web uses the center of the vector line to determine where to cut off the image if the image is scaled down.
But it should use the outer 'edge' of the stroke to cut off the image.
Any ideas to the cause or solution?
P.S.: Yes, I'm a Windows user ;-)

I've ticked Edit>Preferences>General>Use Preview Bounds
That would seem the right way to solve the issue but the problem remains.
Maybe the origin of the issue isn't because of the centre of the path / artwork size.
Since there is no problem (with or without "Use Preview Bounds" ticked) using Save for web while scaling at 100% (or higher).
The clipping only occurs when scaling down.

Similar Messages

  • Illustrator crashes when save for web

    Mac OS X 10.8.4
    Illustrator CS 6
    Everytime I try to do save for web in Illustrator CS6 it gets hung up and I end up having to force quit the program. I have uninstalled and re-installed the software and it works once but then goes back to doing the same thing. I also noticed that now the program is getting hung up when I  try to undo a move or text and again I will have to force quit the program. Any suggestions are greatly appreciated

    Sorry about that here is what i get
    Date/Time:  
    2013-06-13 10:36:15 -0500
    OS Version: 
    10.8.4 (Build 12E55)
    Architecture:
    x86_64
    Report Version:  11
    Command:    
    Illustrator
    Path:       
    /Applications/Adobe Illustrator CS6/Adobe Illustrator.app/Contents/MacOS/Adobe Illustrator
    Version:    
    723 (16.0.0)
    Parent:     
    launchd [144]
    PID:        
    2006
    Event:      
    hang
    Duration:   
    1.12s
    Steps:      
    12 (100ms sampling interval)
    Hardware model:  iMac12,2
    Active cpus:
    4
    Free pages: 
    6968 pages (-2870)
    Pageins:    
    15 pages
    Pageouts:   
    0 pages
    Process:    
    Adobe Illustrator [2006]
    Path:       
    /Applications/Adobe Illustrator CS6/Adobe Illustrator.app/Contents/MacOS/Adobe Illustrator
    Architecture:
    x86_64
    Parent:     
    launchd [144]
    UID:        
    501
    Task size:  
    193628 pages (+6)
    CPU Time:   
    0.001s
      Thread 0x12d6a
    DispatchQueue 1     
    priority 47   
      12 ??? (Adobe Illustrator + 1454936) [0x100163358]
    12 ??? (Adobe Illustrator + 7310260) [0x1006f8bb4]
    12 ??? (Adobe Illustrator + 7376353) [0x100708de1]
    12 ??? (Adobe Illustrator + 7772760) [0x100769a58]
    12 exo::app::OS_AppBase::RunEventLoop() + 55 (exo) [0x108e71747]
    12 -[NSApplication run] + 517 (AppKit) [0x7fff9513d1a3]
    12 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128 (AppKit) [0x7fff95145df2]
    12 _DPSNextEvent + 2073 (AppKit) [0x7fff95146a9f]
    12 _NSHandleCarbonMenuEvent + 245 (AppKit) [0x7fff952248c6]
    12 _HandleMenuSelection2 + 565 (HIToolbox) [0x7fff93e4dec8]
    12 MenuSelectCore(MenuData*, Point, double, unsigned int, OpaqueMenuRef**, unsigned short*) + 605 (HIToolbox) [0x7fff93e4e8bb]
    12 FinishMenuSelection(SelectionData*, MenuResult*, MenuResult*) + 94 (HIToolbox) [0x7fff93e7285f]
    12 SendMenuItemSelectedEvent + 254 (HIToolbox) [0x7fff93e729d3]
    12 SendMenuCommandWithContextAndModifiers + 59 (HIToolbox) [0x7fff93e72a21]
    12 SendHICommandEvent(unsigned int, HICommand const*, unsigned int, unsigned int, unsigned char, void const*, OpaqueEventTargetRef*, OpaqueEventTargetRef*, OpaqueEventRef**) + 443 (HIToolbox) [0x7fff93ecdca9]
    12 SendEventToEventTarget + 40 (HIToolbox) [0x7fff93e96fc9]
    12 SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 410 (HIToolbox) [0x7fff93e811e9]
    12 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1206 (HIToolbox) [0x7fff93e81d1a]
    12 NSSLMMenuEventHandler + 342 (AppKit) [0x7fff95365165]
    12 -[NSCarbonMenuImpl _carbonCommandProcessEvent:handlerCallRef:] + 135 (AppKit) [0x7fff95059097]
    12 -[NSMenu _internalPerformActionForItemAtIndex:] + 36 (AppKit) [0x7fff9505920f]
    12 -[DVAMacMenu performActionForItemAtIndex:] + 61 (dvaui) [0x10862293d]
    12 -[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:] + 133 (AppKit) [0x7fff9536c05a]
    12 -[NSMenuItem _corePerformAction] + 406 (AppKit) [0x7fff9536c36c]
    12 -[NSApplication sendAction:to:from:] + 342 (AppKit) [0x7fff95236959]
    12 -[ExoMacApplication handleMenuCommand:] + 187 (exo) [0x108e73e9b]
    12 void dvacore::config::ExecuteTopLevelFunction<void>(boost::function0<void>, bool*) + 93 (dvacore) [0x107ef497d]
    12 void dvacore::config::ErrorManager::ExecuteFunctionWithTopLevelExceptionHandler<void>(boost::f unction0<void>, bool*) + 250 (dvacore) [0x107ef0e9a]
    12 ??? (Adobe Illustrator + 7781211) [0x10076bb5b]
    12 int dvacore::config::ErrorManager::ExecuteFunction<void>(boost::function0<void>*, void*) + 123 (dvacore) [0x107ef1e0b]
    12 exo::app::OS_AppBase::DispatchMenuCommand(int) + 119 (exo) [0x108e72417]
    12 exo::uisupport::CommandHandlerBase::CallCommandChain(int) + 62 (exo) [0x108ee7ffe]
    12 exo::uisupport::CommandHandler::DoCallMyCommandChain(int) + 36 (exo) [0x108ee85f4]
    12 exo::uisupport::CommandHandler::HandleCommand(int) + 259 (exo) [0x108ee85a3]
    12 ??? (Adobe Illustrator + 7773972) [0x100769f14]
    12 ??? (Adobe Illustrator + 4782547) [0x10048f9d3]
    12 ??? (Adobe Illustrator + 11859237) [0x100b4f525]
    12 ??? (Adobe Illustrator + 9860322) [0x1009674e2]
    12 std::_Rb_tree<SPSUAS, std::pair<SPSUAS const, int>, std::_Select1st<std::pair<SPSUAS const, int> >, std::less<SPSUAS>, std::allocator<std::pair<SPSUAS const, int> > >::erase(SPSUAS const&) + 13900 (Adobe Illustrator) [0x100c951ac]
    12 std::_Rb_tree<SPSUAS, std::pair<SPSUAS const, int>, std::_Select1st<std::pair<SPSUAS const, int> >, std::less<SPSUAS>, std::allocator<std::pair<SPSUAS const, int> > >::erase(SPSUAS const&) + 1228 (Adobe Illustrator) [0x100c9202c]
    12 std::_Rb_tree<SPSUAS, std::pair<SPSUAS const, int>, std::_Select1st<std::pair<SPSUAS const, int> >, std::less<SPSUAS>, std::allocator<std::pair<SPSUAS const, int> > >::erase(SPSUAS const&) + 24282 (Adobe Illustrator) [0x100c97a3a]
    12 ??? (Adobe Illustrator + 9941771) [0x10097b30b]
    12 ??? (Adobe Illustrator + 10209243) [0x1009bc7db]
    12 ??? (Adobe Illustrator + 10207557) [0x1009bc145]
    12 std::_Rb_tree<SPSUAS, std::pair<SPSUAS const, int>, std::_Select1st<std::pair<SPSUAS const, int> >, std::less<SPSUAS>, std::allocator<std::pair<SPSUAS const, int> > >::erase(SPSUAS const&) + 13900 (Adobe Illustrator) [0x100c951ac]
    12 std::_Rb_tree<SPSUAS, std::pair<SPSUAS const, int>, std::_Select1st<std::pair<SPSUAS const, int> >, std::less<SPSUAS>, std::allocator<std::pair<SPSUAS const, int> > >::erase(SPSUAS const&) + 1228 (Adobe Illustrator) [0x100c9202c]
    12 std::_Rb_tree<SPSUAS, std::pair<SPSUAS const, int>, std::_Select1st<std::pair<SPSUAS const, int> >, std::less<SPSUAS>, std::allocator<std::pair<SPSUAS const, int> > >::erase(SPSUAS const&) + 24282 (Adobe Illustrator) [0x100c97a3a]
    12 PluginMain + 744254 (Save4Web) [0x13a8bbeee]
    12 PluginMain + 10078 (Save4Web) [0x13a808b0e]
    12 PluginMain + 6324 (Save4Web) [0x13a807c64]
    12 PluginMain + 314709 (Save4Web) [0x13a853105]
    12 ??? (Save4Web + 104750) [0x13a7f392e]
    12 dvaui::ui::OS_Dialog::RunModal() + 175 (dvaui) [0x1085dd88f]
    12 dvaui::ui::OS_Dialog::ModalLoop() + 177 (dvaui) [0x1085ddbe1]
    12 -[NSApplication runModalSession:] + 49 (AppKit) [0x7fff95390d8e]
    12 -[NSApplication _realDoModalLoop:peek:] + 485 (AppKit) [0x7fff95390659]
    12 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128 (AppKit) [0x7fff95145df2]
    12 _DPSNextEvent + 685 (AppKit) [0x7fff95146533]
    12 BlockUntilNextEventMatchingListInMode + 62 (HIToolbox) [0x7fff93ea8ae3]
    12 ReceiveNextEventCommon + 166 (HIToolbox) [0x7fff93ea8b94]
    12 RunCurrentEventLoopInMode + 209 (HIToolbox) [0x7fff93ea8eb4]
    12 CFRunLoopRunSpecific + 290 (CoreFoundation) [0x7fff94dd00e2]
    12 __CFRunLoopRun + 1529 (CoreFoundation) [0x7fff94dd0ad9]
    12 __CFRunLoopDoTimer + 557 (CoreFoundation) [0x7fff94deb31d]
    12 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20 (CoreFoundation) [0x7fff94deb804]
    12 __NSFireTimer + 96 (Foundation) [0x7fff98dce463]
    12 -[DVAMacNodeTimer fire:] + 118 (dvaui) [0x1085e9476]
    12 void dvacore::config::ExecuteTopLevelFunction<void>(boost::function0<void>, bool*) + 93 (dvacore) [0x107ef497d]
    12 void dvacore::config::ErrorManager::ExecuteFunctionWithTopLevelExceptionHandler<void>(boost::f unction0<void>, bool*) + 250 (dvacore) [0x107ef0e9a]
    12 ??? (Adobe Illustrator + 7781211) [0x10076bb5b]
    12 int dvacore::config::ErrorManager::ExecuteFunction<void>(boost::function0<void>*, void*) + 123 (dvacore) [0x107ef1e0b]
    12 dvaui::ui::OS_NodeTimerData::HandleOSTimerEvent() + 142 (dvaui) [0x1085f395e]
    12 ??? (Adobe Illustrator + 7781211) [0x10076bb5b]
    12 dvaui::ui::OS_NodeTimerData::CallDispatchPossibleTimer(dvaui::ui::OS_NodeTimerData*, dvaui::ui::UI_NodeTimerData*) + 28 (dvaui) [0x1085f209c]
    12 dvaui::ui::UI_Node::UI_DispatchPossibleTimer(dvaui::ui::UI_NodeTimerData*) + 233 (dvaui) [0x10855eb59]
    12 dvaui::ui::UI_SubView::UI_DoTimerNotify(int) + 9 (dvaadameve) [0x10727f4a9]
    12 dvaui::ui::UI_Node::UI_DoTimerNotify(int) + 77 (dvaui) [0x10856272d]
    12 PluginMain + 345462 (Save4Web) [0x13a85a926]
    12 PluginMain + 314653 (Save4Web) [0x13a8530cd]
    12 PluginMain + 321486 (Save4Web) [0x13a854b7e]
    12 PluginMain + 542620 (Save4Web) [0x13a88ab4c]
    12 ??? (Save4Web + 145331) [0x13a7fd7b3]
    12 PluginMain + 3980831 (Save4Web) [0x13abd21cf]
    12 PluginMain + 89934 (Save4Web) [0x13a81c2fe]
    12 ??? (Save4Web + 172283) [0x13a8040fb]
    12 ??? (Save4Web + 152309) [0x13a7ff2f5]
    12 PluginMain + 26658 (Rasterize) [0x110c2e5d2]
    12 PluginMain + 15450 (Rasterize) [0x110c2ba0a]
    12 ??? (Adobe Illustrator + 10385365) [0x1009e77d5]
    12 ??? (Adobe Illustrator + 10501460) [0x100a03d54]
    12 ??? (Adobe Illustrator + 8703269) [0x10084cd25]
    12 ??? (Adobe Illustrator + 10509595) [0x100a05d1b]
    12 ??? (Adobe Illustrator + 10505172) [0x100a04bd4]
    12 ??? (Adobe Illustrator + 10285293) [0x1009cf0ed]
    12 ??? (Adobe Illustrator + 11105157) [0x100a97385]
    12 std::_Rb_tree<SPSUAS, std::pair<SPSUAS const, int>, std::_Select1st<std::pair<SPSUAS const, int> >, std::less<SPSUAS>, std::allocator<std::pair<SPSUAS const, int> > >::erase(SPSUAS const&) + 15393 (Adobe Illustrator) [0x100c95781]
    12 std::_Rb_tree<SPSUAS, std::pair<SPSUAS const, int>, std::_Select1st<std::pair<SPSUAS const, int> >, std::less<SPSUAS>, std::allocator<std::pair<SPSUAS const, int> > >::erase(SPSUAS const&) + 13900 (Adobe Illustrator) [0x100c951ac]
    12 std::_Rb_tree<SPSUAS, std::pair<SPSUAS const, int>, std::_Select1st<std::pair<SPSUAS const, int> >, std::less<SPSUAS>, std::allocator<std::pair<SPSUAS const, int> > >::erase(SPSUAS const&) + 1228 (Adobe Illustrator) [0x100c9202c]
    12 std::_Rb_tree<SPSUAS, std::pair<SPSUAS const, int>, std::_Select1st<std::pair<SPSUAS const, int> >, std::less<SPSUAS>, std::allocator<std::pair<SPSUAS const, int> > >::erase(SPSUAS const&) + 24282 (Adobe Illustrator) [0x100c97a3a]
    12 PluginMain + 280 (BNPlugin) [0x1283b57e8]
    12 PluginMain + 29301 (BNPlugin) [0x1283bc945]
    12 PluginMain + 9949 (BNPlugin) [0x1283b7dad]
    12 PluginMain + 36051 (BNPlugin) [0x1283be3a3]
    12 PSLShutdown + 388 (AdobePSL) [0x1042c58f4]
    12 PSLGetPreferences + 11343 (AdobePSL) [0x1042c540f]
    12 PSLCreateStringUTF8 + 460233 (AdobePSL) [0x104348ce9]
    12 PSLCreateStringUTF8 + 464882 (AdobePSL) [0x104349f12]
    12 PSLSetImageGuides + 1436569 (AdobePSL) [0x1044b0959]
    12 PSSLO::ConstAutoResource<PSSLO::StyleSheet>::ConstAutoResource() + 3318833 (AdobePSL) [0x104036ae1]
    12 PSSLO::ConstAutoResource<PSSLO::StyleSheet>::ConstAutoResource() + 3354840 (AdobePSL) [0x10403f788]
    12 PSSLO::ConstAutoResource<PSSLO::StyleSheet>::ConstAutoResource() + 3353884 (AdobePSL) [0x10403f3cc]
    12 PSSLO::ConstAutoResource<PSSLO::StyleSheet>::ConstAutoResource() + 3353361 (AdobePSL) [0x10403f1c1]
    12 PSSLO::ConstAutoResource<PSSLO::StyleSheet>::ConstAutoResource() + 3346950 (AdobePSL) [0x10403d8b6]
    12 PSSLO::ConstAutoResource<PSSLO::StyleSheet>::ConstAutoResource() + 3342002 (AdobePSL) [0x10403c562]
    12 PSSLO::ConstAutoResource<PSSLO::StyleSheet>::ConstAutoResource() + 5349535 (AdobePSL) [0x10422674f]
    12 PSSLO::ConstAutoResource<PSSLO::StyleSheet>::ConstAutoResource() + 5347308 (AdobePSL) [0x104225e9c]
    12 PSSLO::ConstAutoResource<PSSLO::StyleSheet>::ConstAutoResource() + 5349248 (AdobePSL) [0x104226630]
    12 PSSLO::ConstAutoResource<PSSLO::StyleSheet>::ConstAutoResource() + 5349000 (AdobePSL) [0x104226538]
    12 PSSLO::ConstAutoResource<PSSLO::StyleSheet>::ConstAutoResource() + 5348873 (AdobePSL) [0x1042264b9]
    12 PSSLO::ConstAutoResource<PSSLO::StyleSheet>::ConstAutoResource() + 5514742 (AdobePSL) [0x10424eca6]
    12 PSSLO::ConstAutoResource<PSSLO::StyleSheet>::ConstAutoResource() + 5514524 (AdobePSL) [0x10424ebcc]
    12 ??? (AdobePSL + 118211) [0x103cf6dc3]
    12 ??? (AdobePSL + 117947) [0x103cf6cbb]
    12 ??? (AdobePSL + 117606) [0x103cf6b66]
    12 PSSLO::ConstAutoResource<PSSLO::StyleSheet>::ConstAutoResource() + 569177 (AdobePSL) [0x103d97609]
    12 PSSLO::ConstAutoResource<PSSLO::StyleSheet>::ConstAutoResource() + 580792 (AdobePSL) [0x103d9a368]
    12 PSSLO::ConstAutoResource<PSSLO::StyleSheet>::ConstAutoResource() + 5501139 (AdobePSL) [0x10424b783]
    12 PSSLO::ConstAutoResource<PSSLO::StyleSheet>::ConstAutoResource() + 579476 (AdobePSL) [0x103d99e44]
    12 PSSLO::ConstAutoResource<PSSLO::StyleSheet>::ConstAutoResource() + 585837 (AdobePSL) [0x103d9b71d]
    12 __psynch_mutexwait + 10 (libsystem_kernel.dylib) [0x7fff9275a122]
    *12 psynch_mtxcontinue + 0 (mach_kernel) [0xffffff80005b4550]
      Thread 0x12d78
    DispatchQueue 2     
    priority 49   
      12 _dispatch_mgr_thread + 54 (libdispatch.dylib) [0x7fff8e4d89ee]
    12 kevent + 10 (libsystem_kernel.dylib) [0x7fff9275ad16]
    *12 ??? (mach_kernel + 3471808) [0xffffff800054f9c0]
      Thread 0x12d80
    priority 47   
      12 thread_start + 13 (libsystem_c.dylib) [0x7fff8dd091e1]
    12 _pthread_start + 327 (libsystem_c.dylib) [0x7fff8dd1c7a2]
    12 PrivateMPEntryPoint + 58 (CarbonCore) [0x7fff903067e0]
    12 ??? (AdobeACE + 230874) [0x102a325da]
    12 ??? (AdobeACE + 234185) [0x102a332c9]
    12 MPWaitOnQueue + 252 (CarbonCore) [0x7fff90291a98]
    12 TSWaitOnConditionTimedRelative + 132 (CarbonCore) [0x7fff9032f3e7]
    12 TSWaitOnCondition + 108 (CarbonCore) [0x7fff9032f210]
    12 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x7fff9275a0fa]
    *12 psynch_cvcontinue + 0 (mach_kernel) [0xffffff80005b5bb0]
      Thread 0x12d81
    priority 47   
      12 thread_start + 13 (libsystem_c.dylib) [0x7fff8dd091e1]
    12 _pthread_start + 327 (libsystem_c.dylib) [0x7fff8dd1c7a2]
    12 PrivateMPEntryPoint + 58 (CarbonCore) [0x7fff903067e0]
    12 ??? (AdobeACE + 230874) [0x102a325da]
    12 ??? (AdobeACE + 234185) [0x102a332c9]
    12 MPWaitOnQueue + 252 (CarbonCore) [0x7fff90291a98]
    12 TSWaitOnConditionTimedRelative + 132 (CarbonCore) [0x7fff9032f3e7]
    12 TSWaitOnCondition + 108 (CarbonCore) [0x7fff9032f210]
    12 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x7fff9275a0fa]
    *12 psynch_cvcontinue + 0 (mach_kernel) [0xffffff80005b5bb0]
      Thread 0x12d82
    priority 47   
      12 thread_start + 13 (libsystem_c.dylib) [0x7fff8dd091e1]
    12 _pthread_start + 327 (libsystem_c.dylib) [0x7fff8dd1c7a2]
    12 PrivateMPEntryPoint + 58 (CarbonCore) [0x7fff903067e0]
    12 ??? (AdobeACE + 230874) [0x102a325da]
    12 ??? (AdobeACE + 234185) [0x102a332c9]
    12 MPWaitOnQueue + 252 (CarbonCore) [0x7fff90291a98]
    12 TSWaitOnConditionTimedRelative + 132 (CarbonCore) [0x7fff9032f3e7]
    12 TSWaitOnCondition + 108 (CarbonCore) [0x7fff9032f210]
    12 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x7fff9275a0fa]
    *12 psynch_cvcontinue + 0 (mach_kernel) [0xffffff80005b5bb0]
      Thread 0x12d8f
    priority 47   
      12 thread_start + 13 (libsystem_c.dylib) [0x7fff8dd091e1]
    12 _pthread_start + 327 (libsystem_c.dylib) [0x7fff8dd1c7a2]
    12 AGMInitialize + 3288447 (AdobeAGM) [0x102ee9d8b]
    12 AGMInitialize + 3259120 (AdobeAGM) [0x102ee2afc]
    12 AGMInitialize + 3255535 (AdobeAGM) [0x102ee1cfb]
    12 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x7fff9275a0fa]
    *12 psynch_cvcontinue + 0 (mach_kernel) [0xffffff80005b5bb0]
      Thread 0x12d9b
    priority 47   
      12 thread_start + 13 (libsystem_c.dylib) [0x7fff8dd091e1]
    12 _pthread_start + 327 (libsystem_c.dylib) [0x7fff8dd1c7a2]
    12 APXGetHostAPI + 2516713 (adbeapeengine) [0x117f9ae79]
    12 APXGetHostAPI + 2516410 (adbeapeengine) [0x117f9ad4a]
    12 APXGetHostAPI + 2516289 (adbeapeengine) [0x117f9acd1]
    12 APXGetHostAPI + 83761 (adbeapeengine) [0x117d48ec1]
    12 APXGetHostAPI + 2516093 (adbeapeengine) [0x117f9ac0d]
    12 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x7fff9275a0fa]
    *12 psynch_cvcontinue + 0 (mach_kernel) [0xffffff80005b5bb0]
      Thread 0x12d9c
    priority 47   
      12 thread_start + 13 (libsystem_c.dylib) [0x7fff8dd091e1]
    12 _pthread_start + 327 (libsystem_c.dylib) [0x7fff8dd1c7a2]
    12 APXGetHostAPI + 2516713 (adbeapeengine) [0x117f9ae79]
    12 APXGetHostAPI + 2516410 (adbeapeengine) [0x117f9ad4a]
    12 APXGetHostAPI + 2516289 (adbeapeengine) [0x117f9acd1]
    12 APXGetHostAPI + 83761 (adbeapeengine) [0x117d48ec1]
    12 APXGetHostAPI + 2516093 (adbeapeengine) [0x117f9ac0d]
    12 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x7fff9275a0fa]
    *12 psynch_cvcontinue + 0 (mach_kernel) [0xffffff80005b5bb0]
      Thread 0x12d9d
    priority 47   
      12 thread_start + 13 (libsystem_c.dylib) [0x7fff8dd091e1]
    12 _pthread_start + 327 (libsystem_c.dylib) [0x7fff8dd1c7a2]
    12 APXGetHostAPI + 2516713 (adbeapeengine) [0x117f9ae79]
    12 APXGetHostAPI + 2516410 (adbeapeengine) [0x117f9ad4a]
    12 APXGetHostAPI + 2516289 (adbeapeengine) [0x117f9acd1]
    12 APXGetHostAPI + 83761 (adbeapeengine) [0x117d48ec1]
    12 APXGetHostAPI + 2516093 (adbeapeengine) [0x117f9ac0d]
    12 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x7fff9275a0fa]
    *12 psynch_cvcontinue + 0 (mach_kernel) [0xffffff80005b5bb0]
      Thread 0x12d9e
    priority 47   
      12 thread_start + 13 (libsystem_c.dylib) [0x7fff8dd091e1]
    12 _pthread_start + 327 (libsystem_c.dylib) [0x7fff8dd1c7a2]
    12 APXGetHostAPI + 2516713 (adbeapeengine) [0x117f9ae79]
    12 APXGetHostAPI + 2516410 (adbeapeengine) [0x117f9ad4a]
    12 APXGetHostAPI + 2516289 (adbeapeengine) [0x117f9acd1]
    12 APXGetHostAPI + 83761 (adbeapeengine) [0x117d48ec1]
    12 APXGetHostAPI + 2516093 (adbeapeengine) [0x117f9ac0d]
    12 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x7fff9275a0fa]
    *12 psynch_cvcontinue + 0 (mach_kernel) [0xffffff80005b5bb0]
      Thread 0x12da0
    priority 63   
      12 t

  • Help - problem with save for web when jpg image is placed in file

    I have a jpg image that I placed in my Illustrator 5 file to use as a backdrop and then created several vector buttons on top.  When I attempt to create an arboard around a single button and then save for web, it ignores the artboard dimensions and shows the entire jpg dimensions.  If I create the same file without the jpg backdrop image, I am able to use the artboards to save just a single button.  Any time I place a jpg image in my Illustrator file and attempt to use the artboards, the artboards are ignored and the entire area of the jpg is saved.  I am able to use the slice tool to do the saving, but I prefer to use the artboards.  Does anyone have any suggestions on how to get the artboards to work when a jpg is placed in the file?  Thanks.

    THANK YOU!!!
    It says, "Clip to artboard".  I wasn't sure what clip meant, but that was it!  Thank you.

  • A different take on the "Save For Web" color shift issue...

    Ok, everyone who has fussed much with photoshop and "Save For Web" knows about the color shift issue. If you want your colors to look right after you "save for web", you have to work in the sRGB colorspace, and have Proof Colors checked (soft proofing on) and the proof color setup set to Monitor RGB, otherwise what you get looks terrible when displayed in a browser.
    But of course if you are editing for print, this is exactly what you DON'T want to do. Well, I work in both. In fact, often the same images, and I want them to appear as close as reasonably possible in both print and web formats, and without a lot of fussing on my part. And I'm pickiest about the print mode, since I have the most control there, so that's the way I want to edit by default.
    Nothing new here.
    Now comes the interesting part (in my mind, anyway). Obviously there is a known remapping -- because PhotoShop DOES it when you select Proof Colors. So the inverse mapping must also be known (with some gamut issues, but I'm not concerned with those, because, after all, I'm VIEWING it on a monitor anyway!). What I want is a plug-in that automatically applies that inverse mapping so that, when I do a Save For Web, I end up with the colors I've been viewing all the time when setting the shot up in print mode. Then, too, I don't have to worry about what mode I'm in when I'm editing -- it just fixes it when doing a save-for-web.
    Again, I want to edit in my normal print mode (typically ProPhoto colorspace, and with soft-proofing off or set to the printer/medium combination I expect to use), then do a single operation (might be a multi-step action) to "screw up" my colors so that when I then do a "Save-For-Web", the resulting image, when viewed on the average color-stupid browser, looks like the image I've been seeing in Photoshop.
    Anyone know of such a beast?   I would gladly pay for a plug-in that really works and fixes the problem.
    And if you have other solutions, I'm interested, but the absolute requirement is that it I do one single edit pass for my colors for both print and web use, and I get what I see on the screen in PS on both the prints and on the web display (i.e., working in sRGB/Monitor RGB mode all the time won't cut it). And PREFERABLY, let me do all my editing work in the ProPhoto (or at least AdobeRGB) colorspace so I have a gamut closer to what the printer can do.
    Anyone got a decent solution for this?

    Sorry, I think I'm being unclear.  This has nothing to do with individual monitor profiles.  In Proof Setup, "Monitor RGB" amounts to turning off ALL color management, and simply letting the monitor do what it will.  It is what the vast majority of web browsers do (even if the operating system provides color management, the browsers don't take advantage of it), so that is what you need to consider for images that will be viewed on a web browser.  If you convert your image to sRGB,  select Monitor RGB in Proof Set up, and turn on Proof Colors, you will see the image as it would appear on a web browser (after you save it as a jpg or use "Save For Web/Devices" to save it as a jpg).   Since almost everyone is running different uncalibrated monitors, there will be lots of variation in how it will look to them, so precise control of the color is unimportant.
    That said, I would expect the color on a calibrated monitor (such as the one I use when editing) to be reasonably close to the colors I am seeing while editing in PS.  To the extent a monitor deviates from "calibrated", those colors will vary, but a good monitor should show good colors.   Unfortunately, this is NOT the case, as my previous post shows.  The colors produced by the steps above are oversaturated and significantly shifted in hue.  There is, to my mind, anyway, no reason for this.  Adobe clearly knows what the mapping is between the colors as it displays them in PS and the un-controlled "Monitor RGB" -- that is, it is the color map they are using during normal editing display.  If they were to reverse-apply that map prior to saving it as a jpg, then the image would appear on a browser on that same (presumably calibrated) monitor very similar to what you set up when editing.  Anyone else viewing the image on a web browser with a calibrated monitor would also see good colors.  To the extent other viewers' monitors are out of calibration, their colors will suck, but there's nothing you can do about that.
    I guess in some sense I AM "asking for a Color-Mamangement-solution for a "non-Color-Management-situation", but specifically I'm asking for PS Color Management to do the best it can for non-Color-Managed situations that we all face every day.
    Does that make more sense?

  • Looking for a better solution to the "Save for web" color shift issue

    Ok, everyone who has fussed much with photoshop and "Save For Web" knows about the color shift issue. If you want your colors to look right after you "save for web", you have to work in the sRGB colorspace, and have Proof Colors checked (soft proofing on) and the proof color setup set to Monitor RGB, otherwise what you get looks terrible when displayed in a browser.
    But of course if you are editing for print, this is exactly what you DON'T want to do. Well, I work in both. In fact, often the same images, and I want them to appear as close as reasonably possible in both print and web formats, and without a lot of fussing on my part. And I'm pickiest about the print mode, since I have the most control there, so that's the way I want to edit by default.
    Nothing new here.
    Now comes the interesting part (in my mind, anyway). Obviously there is a known remapping -- because PhotoShop DOES it when you select Proof Colors. So the inverse mapping must also be known (with some gamut issues, but I'm not concerned with those, because, after all, I'm VIEWING it on a monitor anyway!). What I want is a plug-in that automatically applies that inverse mapping so that, when I do a Save For Web, I end up with the colors I've been viewing all the time when setting the shot up in print mode. Then, too, I don't have to worry about what mode I'm in when I'm editing -- it just fixes it when doing a save-for-web.
    Again, I want to edit in my normal print mode (typically ProPhoto colorspace, and with soft-proofing off or set to the printer/medium combination I expect to use), then do a single operation (might be a multi-step action) to "screw up" my colors so that when I then do a "Save-For-Web", the resulting image, when viewed on the average color-stupid browser, looks like the image I've been seeing in Photoshop.
    Anyone know of such a beast?   I would gladly pay for a plug-in that really works and fixes the problem.
    And if you have other solutions, I'm interested, but the absolute requirement is that it I do one single edit pass for my colors for both print and web use, and I get what I see on the screen in PS on both the prints and on the web display (i.e., working in sRGB/Monitor RGB mode all the time won't cut it). And PREFERABLY, let me do all my editing work in the ProPhoto (or at least AdobeRGB) colorspace so I have a gamut closer to what the printer can do.
    Anyone got a decent solution for this?

    Chris
    I spent all day Googling and doing side by side comparisons of my old and new systems.
    My display is a Dell U2410. It has several presets, including sRGB and Adobe RGB. I've been using sRGB.
    On my OLD system, (Win XP, PsCS2, DwCS4) there seems to be no distinction between color managed and non color managed apps, even on this wide gamut display. I could capture (digital camera) in Adobe RGB, open and edit in PsCS2, save as .psd, convert to CMYK for print, or convert to sRGB for SFW. All images looked identical and they printed and displayed perfectly. I thought this was normal, and seemed logical. This also seems to be the source of my incorrect assumptions. I was trying to get my new machine to behave like my old one.
    So I get this new machine (Windows 7, PsCS5, DwCS5) and now (still in sRGB display mode) all color managed apps appear de-saturated. Non color managed apps are OK. If I switch the display to Adobe RGB, color managed apps are OK, but non color managed apps are way too saturated. From my investigation, I believe this is normal behavior on a wide gamut display. I've tried changing the Control Panel > Display > Screen Resolution > Advanced settings > Color Management options, but to no avail. Either I'm missing something, or Windows 7 is doing color management differently.
    It seems my only option now is to use Adobe RGB display setting for Ps, etc. and switch to sRGB for Dw and non color managed apps. Or, have 2 separate files for print and web. I've Googled 'til my eyes are numb and still not sure I'm getting this. Any enlightenment would be greatly appreciated.
    Finally, I don't see an edit function here, so I can't remove my previous incorrect reply. Moderator, please feel free to do so.
    Thanks

  • How to Save for Web in the correct size?

    So i created a new project in Illus. CS5 with an artboard size of 700x150 pixels. I have two graphics in there that are about 215 pixels tall so part of it flies off the artboard, but i have a clipping part that hides all the parts that i dont want to see.
    The problem is when i go to Save for Web, the ouput image is 700x215 because it includes the space used by the graphics, that fly off the board, but you dont even see it. I was able to get around this by opening the file in photoshop and then cropping to 700x150 so the extra space is removed, but there should be a way to save this in Illus. without the hassel.
    Any suggestions would be appreciated...

    Thanks, that worked. I figure there was a setting in there somewhere and was even in the right tab, but didnt think to click on that.

  • Save For Web Saturates Colors

    Hello,
    I've dealt with this before and searched the internet for a solution/fix, but still have the problem of JPG images appearing over-saturated when viewing them in a web browser compared to the way they look in PS CS4 or in the windows "preview" application.
    Here's the workflow:
    Work with an image in PS CS4 (Vista) with an assigned color profile of sRGB. Use the "save for web" dialog to create a JPG (with the "convert to sRGB" box checked). View the image in Windows by right-clicking and selecting "preview," and it looks fine (looks same as it does within PS). View the same image using Firefox 3 or Internet Explorer 7, and it appears oversaturated (mosty too reddish) as compared to the original.
    I've tried various permutations to the above (e.g., turning off "convert to sRGB") with no avail. However, if I convert to LAB color, and then save for web, the resulting image appears less saturated overall, even though it still appears more saturated as viewed in a web browser as compared to PS/Windows-preview.
    Does anyone have any further suggestions to get the images to appear the same in a browser as they do in PS or in the Windows Photo Gallery (preview)?
    thanks,
    JP

    Silkrooster wrote:
    What happens if you use save as? I believe that save for web does not save the color profile therefore firefox or IE might assume a different profile thus over saturated images. I have read someplace that firefox uses color profiles but I am not sure about IE.
    Firefox is not colour managed by default. It has to be enabled by the user.

  • CS4 Save For Web not the right size

    I'm having problems with Illustrator images when I use the Save For Web. The image size always comes out the same size as my artboard. In other words I set up a new document to be letter size, create my drawing within that document. My drawing is only about 300 px by 150 px. When I Save for Web my image is the same size as the document or artboard not my drawing. Is this something new in CS4? Do I have a preference set incorrectly? The only way I have found to get rid of the background is to adjust the size of the artboard manually. Is there a way to adjust the artboard to fit my drawing automatically, like cropping to an object in Photoshop?

    CS,
    Basically the same issue was up, and answered, recently here:
    http://forums.adobe.com/message/2667045

  • Photoshop slice tool and Save for Web image quality. Will it affect prints?

    I want to slice a large photo into multiple smaller (4x6) printable photos to arrange in a 12x12 inch scrapbook binder pocket (made of of 4x6 pockets). I need to order separate 4x6s online so tiling in the print options is not what I need.
    The slow way I know to do this involves cropping and saving each section (maybe even recording this action to do batch processing). However, another way is to use the slice tool to quickly divide up the sections then "Save for Web...". I can adjust some parameters, but I'm afraid there are other automatic adjustments that I don't want. For example, all images are converted to 96 dpi instead of the original 300 dpi. The number of pixels remains the same so I don't think there will be problems printing the picture.
    My question is: does the Save for Web function reduce image quality in any way when printing (it is obviously intended to be used to optimize images for websites)? Are there settings in "Save for Web" that would optimize for high quality prints? Is there a better way to tile an image?
    I have not yet compared any prints.
    W7
    CS6

    If you understand that something will do something you do not want like convert to 96 DPI as long as it does not resample you can always convert back to 300 DPI. If you want 6 4x6 to form a 12x12 you must start with an square 1:1 aspect ratio image. That you resample to 12"x 12" at 300 dpi if you want 6 4x6 300 dpi images.
    If the original images vary in size and aspect ratio you need to crop them square or add two borders to make them square.   The rest is easy to do with an action.
    The square crop or border can be automated with a little scripting.  If crop  a center crop would be the route to go. My crafting actions package contains  more the a dozen scripts to be used within action. One is a plug-in script that would make center cropping a snap two steps menu File>Automat>AspectsRatioSelection followed menu Image>Crop.  Add a menu Image>Size set side to 12" and resolution 300 DPI and you have your  starting 12"x12" 300 dpi image.
    Flatten the image make your first 4"x6" selection copy past to add it as a layer. Select the background select the next 4x6 area copy and paste repeat that process till you have added the 6 4"X6" layers. Then delete the background, Select all, target all layers and use layer>Align layers to selection>Top edge then repeat align to left edge. the Image>Trim you have your 6 4x6 in a stack.   You can the use Adobe Photoshop Script Export Layer to file.   All automated in an action however the last step Export layers to files is interactive for its not a plug-in script. So if you batch it you keen to hang around to interact with the last step for each image.
    You could also write you own export script that would not need human intervention to use instead of Adobe interactive script.
    Crafting Actions Package UPDATED Aug 10, 2014 Added Conditional Action steps to Action Palette Tips.
    Contains
    Action Actions Palette Tips.txt
    Action Creation Guidelines.txt
    Action Dealing with Image Size.txt
    Action Enhanced via Scripted Photoshop Functions.txt
    CraftedActions.atn Sample Action set includes an example Watermarking action
    Sample Actions.txt Photoshop CraftedActions set saved as a text file.
    More then a dozen Scripts for use in actions
    Example
    Download

  • Ps 3d and filters and save for web are not working the way they should

    At work we just put cs6 on a w7 machine running 64 bit which has more than that required mem and or ram to run cs6 - unfortunately I have to use a windows based machine at work (cheapskates). Anyways. I see the 3d menus and the filter menu in PS but they aren't funtional. The filter menu drop down is there but Liquify is the only one that shows up the rest are gray. The option to choose 3d is also there but they are not functional (grayed out) - I took a look at some online tutorials on using the 3d effect in PS CS6 and Ive gone through it a few times and it still won't work for me. Also, in illustrator when I save for web - when I adjust the pixel dimensions and move the mouse over and click on the image that I am saving for web nothing happens and I'm completely boggled about how to get the image size to change in the save for web pane. Typically I am used to being able to input the the number into the pixel dimenion field and click on the image and the image resizes (on a mac you can either click on the image or hit return and the image will resize in front of your eyes!). I am unable to get this to work the way I am used to, this happens for me in both ill5 and ill6 on this piece of crap windows machine. Maybe I just need to reinstall? Maybe adobe has changed the way this works? Maybe a sledge hammer into this windows machine would solve all my problems!? IDK. someone help... help me... pleeeeaaaaaaaaaaasssseeeee

    unfortunately I have to use a windows based machine at work (cheapskates).
    This gets a "stupid comment of the day" medal. Seriously. These days Macs are just as convoluted and effed up as Windows was a few years ago - nice as long as everything works, but god forbid you have a problem. So by all means, update your graphics driver and be glad that you actually have that choice rather than having to wait half a year for Apple to fix it...
    Mylenium

  • Save For Web Error in CS6

    When I try saving an Illustrator file using Save For Web in CS6, if the file isn't split up into slices I get an error "Could not complete this operation. There are no user slices." If I open the file in CS5, it exports perfectly fine (and with the XHTML page creation that used to be part of Save For Web that I'm pissed has been stripped out...)
    Can anybody explain why this is happening? I never had to create slices to make images export w/ Save For Web in the past.

    I had this problem too. I think I've fixed it.
    Try:
    Open Illustrator and start a new document.
    Create a new slice (Shift+K) anywhere on the document.
    File > Save for Web...
    In the bottom right corner there is an option for “Export”. Change this to “All Slices”.
    Save that out  so that Illustrator retains that option as default.
    Hope that helps.

  • Pixelation / Distortion when using "Save for Web..." versus "Export"

    Hi. When I export from Illustrator using the Save for Web & devices option (I export the original at png24) the images are not as smooth as those produced by selecting File-Export. 2 images produced by both images are attached. The variation is most noticeable on the round corners.
    Is there a way to export work at full quality using the Save for Web & Devices option?

    jkadobeil,
    I have transparency ticked. One cannot specify matte if transparency is ticked.
    I can in 10. It may be a bug or corrupted preferences. If the latter, you may try to Ctrl/Cmd+Alt/Option+Shift during startup or Move the folder with Illy closed.

  • Save For Web vs. Resizing vs. File Size vs. PNG

    In playing around with some settings while saving a .png file, I noticed some weird results. For this example, the original image is 300 x 300, but I want the final size to be 200 x 200. I get different results depending on the order I perform the following operations (I never thought the order mattered until now).
    1. start with 300 x 300 image, choose save for web, select png-24, with transparency, white matte, convert to sRGB, change image size to 200 x 200, then save - the file size is 37kb
    2. start with 300 x 300 image, use Photoshop's "image size" to change to 200 x 200, then save for web, etc - the file size is 111kb
    So depending on which step I resize the image, the file size is significantly different - if I resize BEFORE using save for web, the file size is much larger. This is just weird to me, but I always resize AFTER choosing save for web, so that's why I've never caught this until now. In case you ask, while using Photoshop's "image size", all three options are checked at the bottom of that window, so nothing is getting re-sampled or anything like that.
    The only thing I can think of is each of those methods treat pixel data differently when reducing the dimensions. When I overlay both exported .png files on top of each other, I see no difference in pixel quality and/or color shift - so why the big difference in file size? Unsurprisingly, if I just save the file straight to .png, the sharpness is much better, and the file size is 46kb. I did notice when saving for web, the colors become a little more saturated.
    Are all these results typical? I've never really paid much attention to the results when exporting .png's. I always thought the results were lossless (in general).

    Too many variables
    What? There are 2 variables here (variables = scenarios = steps). Only two different operations.
    1. resize the image, THEN use "save for web" = 91kb
    2."save for web", THEN change image size = 157kb
    Hopefully my logic translates here:
    All other settings are the same. I even made sure the .psd was sRGB this time. The specific question was "why does the different workflow order produce such a big difference in file size"?
    In creating a new test file (http://www.shan-dysigns.com/userForums/photoshop/savePNG.zip), I did notice an interesting thing: (I'm including my files in case you want to follow along or test for yourself)
    If I merge all layers BEFORE performing the steps above, the file sizes were relatively closer to one another - 168kb and 157kb (respectively from the 1, 2 list above)
    One thing to note is all the .psd layers are either shapes or text - this whole scenario may be totally different if each layer had rasterized content (actually, it does, by about -20kb).
    The file size in step 1 above didn't jump until it had to consider rastered text/shapes into the calculation. So all this tells me the difference in file size has to do with how each process handles vector data. Maybe when you allow PS to resize the image first, the overall file size is smaller because the vector data gets recalculated???
    I don't know how to properly interpret all these differences, but I do know there is something about PS's operation of resizing the canvas with vector data versus resizing the canvas with rasterized data - this has to be where the difference in file size lies.
    Maybe I've just wasted a bunch of time on the obvious, but I think I learned something here. Now my head hurts and my eyes have popped out of my head.
    So, Chris, I guess there ARE more variables in this situation. My curse is being nosey and wanting to know more technically about PS than most casual designers probably would care about.

  • Photoshop CS3 color management "Save for Web" problem

    This problem is getting the best of me.......
    After spending 3 full days researching this problem, I am no closer to finding an answer than when I started. I still cannot produce a usable image through the "Save for Web" feature of Photoshop CS3. I have read web page after web page of "Tips, Tricks and Recommendations" from dozens of experts, some from this forum, and still I have no solution... I am exhausted and frustrated to say the least. Here's the simple facts that I know at this point.
    I have a web design project that was started in PS CS1. All artwork was created in photoshop and exported to JPG format by using "Save for Web". Every image displays correctly in these browsers (Safari, Camino, FireFox and even Internet Explorer on a PC).
    I have recently upgraded to PS CS3 and now cannot get any newly JPG'd image to display correctly. My original settings in CS1 were of no concern to me at the time, because it always just worked, and so I do not know what they were. I have opened a few of my previous images in CS3 and found that sRGB-2.1 displays them more or less accurately. I am using sRGB 2.1 working space. Upon openning these previous image files, I get the "Missing Profile" message and of course I select "Leave as is. Do Not color manage". CS3 assumes sRGB-2.1 working space, opens the file, and all is well.
    The problem is when I go to "Save for Web", the saturation goes up, and the colors change. The opposite of what most people are reporting. Here's another important point... new artwork created in CS3 does exactly the same thing, so it's not because of the older CS1 files.
    I have tried every combination of "uncompensated color", "Convert to sRGB", "ICC Profile", etc. while saving. I have Converted to sRGB before saving, and my monitor is calibrated correctly.
    I have tried setting the "Save for Web" page on 2-up and the "original" on the left is already color shifted before I even hit the "Save" button. Of course, the "Optimized" image on the right looks perfect because I am cheating by selecting the "Use Document Color Profile" item. Why do they even have this feature if doesn't work, or misleads you?
    Does anyone have any ideas what could be happening here? Why is this all so screwed up?
    CS1 worked fine out of the box.
    Final note: I do have an image file I could send along that demonstrates how it is possible to display an image exactly the same in all 4 of the browsers I mentioned with no color differences. It is untagged RGB and somehow it just works.
    I am very frustrated with all of this and any suggestions will be appreciated
    Thanks,
    Pete

    >> First of all... I'm using an Adobe RGB image master... I open it and get the Profile Mismatch Screen... I choose Use Enbedded profile... all looks well. Next I go to Proof Setup > Monitor RGB... again all looks well, no change that I can tell.
    This has further confused the issue on several points, not the least of which version PS you are doing this with?
    >> AdobeRGB> Convert to Profile > Working Space sRGB-2.1... all still looks well... but now, when I go to Proof Setup > Monitor RGB... I see the insane oversaturated look that is driving me nuts.
    That is your strongest clue...it sounds like you have a bad system or bad monitor profile. To rule out the monitor profile: Set sRGB as your monitor profile in System Prefs> Displays> Color.
    >> Adobe RGB image master... I open it and get the Profile Mismatch Screen... I choose Use Enbedded profile... all looks well. Next I go to Proof Setup > Monitor RGB... again all looks well
    That doesn't make sense, stripping an embedded AdobeRGB profile should desaturate the color in Softproof MonitorRGB, especially the reds -- you have something wacky going on there.
    At this point I think you need to review the links and get a grip about how color management and profiles work...
    BTW, forget about setting ColorSync in PS COlor Settings, use Adobe ACE.
    MO,
    I think SFW is fixed under CS3 :) By default it Converts to sRGB and strips the profile.

  • Save for Web- 6000 Images

    I use Photoshop Elements 12.  We need to run save for web on 6000 images.  I am assuming an action file is the fastest way of doing this.  Can we create an action file on a MAC and run it on PE 12 on a windows PC?  I am thinking no because the directory structures are different.  Open for any suggestions

    Did you consider using either the 'process multiple files' feature in the editor or the 'export' feature in the organizer?
    Both let you state wich pixel size and compression level you want.
    If you are worried about leaving IPTC metadata like captions, you can delete them from the organizer. For keywords, I think you'd need an exif editor.
    Edit:
    If you have the very affordable Elements+ there is a script enabling you to run a batch with 'save for web':
    "Batch Optimized" Category

Maybe you are looking for