<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>sidecar files &amp; non-destructive editing on darktable 5.6 user manual</title>
    <link>https://docs.darktable.org/usermanual/5.6/en/overview/sidecar-files/</link>
    <description>Recent content in sidecar files &amp; non-destructive editing on darktable 5.6 user manual</description>
    <generator>Hugo</generator>
    <language>en</language>
    <atom:link href="https://docs.darktable.org/usermanual/5.6/en/overview/sidecar-files/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>sidecar files</title>
      <link>https://docs.darktable.org/usermanual/5.6/en/overview/sidecar-files/sidecar/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.darktable.org/usermanual/5.6/en/overview/sidecar-files/sidecar/</guid>
      <description>&lt;p&gt;darktable is a non-destructive image editor and opens all images in read-only mode. Most data created within darktable (metadata, tags, and image processing steps) is stored in separate &lt;code&gt;.XMP&lt;/code&gt; &lt;em&gt;sidecar&lt;/em&gt; files. These files are stored alongside the original Raw files and allow darktable to store information about the images as well as the full editing history without touching the original raw files. When you import an image into darktable for the first time, an XMP file is automatically generated. The generation of XMP files can be disabled in &lt;a href=&#34;https://docs.darktable.org/usermanual/5.6/en/preferences-settings/storage/#xmp-sidecar-files&#34;&gt;preferences &amp;gt; storage &amp;gt; XMP sidecar files&lt;/a&gt; but this is not recommended in normal use.&lt;/p&gt;</description>
    </item>
    <item>
      <title>importing sidecar files generated by other applications</title>
      <link>https://docs.darktable.org/usermanual/5.6/en/overview/sidecar-files/sidecar-import/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.darktable.org/usermanual/5.6/en/overview/sidecar-files/sidecar-import/</guid>
      <description>&lt;p&gt;When importing an image, darktable automatically checks if it is accompanied by a sidecar file. As well as looking for files named &lt;code&gt;&amp;lt;basename&amp;gt;.&amp;lt;extension&amp;gt;.xmp&lt;/code&gt; and &lt;code&gt;&amp;lt;basename&amp;gt;_&amp;lt;number&amp;gt;.&amp;lt;extension&amp;gt;.xmp&lt;/code&gt; (darktable&amp;rsquo;s XMP file naming formats) darktable also checks for the presence of a file in the form &lt;code&gt;&amp;lt;basename&amp;gt;.xmp&lt;/code&gt; (the naming format for Lightroom&amp;rsquo;s XMP sidecar files). Files with the latter naming format will be read by darktable but will not be written to. Once the image has been imported, darktable will generate an additional XMP file using its own naming convention.&lt;/p&gt;</description>
    </item>
    <item>
      <title>local copies</title>
      <link>https://docs.darktable.org/usermanual/5.6/en/overview/sidecar-files/local-copies/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://docs.darktable.org/usermanual/5.6/en/overview/sidecar-files/local-copies/</guid>
      <description>&lt;p&gt;Many users have huge image collections stored on extra hard drives in their desktop computer, or on an external storage medium (RAID NAS, external hard drives etc.).&lt;/p&gt;&#xA;&lt;p&gt;It is a common requirement to develop a number of images while travelling using a laptop and then later synchronize them back to the original storage medium. However, copying images manually from the main storage to the laptop and back is cumbersome and prone to errors. The “local copies” feature of darktable has been designed to directly support these use cases.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
