Comparison
PaperKeepsake vs Mylio Photos
Mylio Photos is a library that lives with the family across their own devices, and PaperKeepsake is the studio side record of the work that fills a library like that.
Comparison
Lightroom Classic is a photographer's catalog and darkroom, and PaperKeepsake is the project record for other families' originals moving through your studio.
If your week is spent improving images, Lightroom Classic is the stronger tool and nothing here changes that. If your week is spent taking custody of four boxes from a client, running them through a feeder in numbered batches, guessing at a decade from a hairstyle and a car in the background, and handing back an index her brother can search, a photographer's catalog is the wrong shape for the job. PaperKeepsake tracks the project, the boxes and the people in them. Many organizers run both: correction in Lightroom, archive record in PaperKeepsake.
| What you are deciding | PaperKeepsake | Adobe Lightroom Classic |
|---|---|---|
| What the software organizes | A client archive project, one per family, with box and batch counts | A catalog of images, generally ones the operator shot or is editing |
| Whose photographs | Originals owned by a client, held in custody and returned to her | Built around a photographer's own growing library |
| Dating undated prints | Circa ranges and decade tags for prints with nothing written on the back | Organizes around a capture date the camera recorded |
| Person tagging | Named relatives across generations, with unknown faces held open until a sibling identifies them | Keyword and face tools aimed at a photographer's recurring subjects |
| Scanning batches | Batch numbers tied to a physical box, so a rescan is traceable months later | Imports arrive as folders, with no concept of the box on your shelf |
| Family handoff | A shareable family index the client and her relatives can search themselves | Export, album and publishing features aimed at photography clients |
| Image correction | None, capture and color work stay in the software you already use | Full raw processing, color, dust removal and retouching |
| Studio staffing | Seats by tier, from Solo Organizer through Studio and Team | Assumes an editor working a catalog at a workstation |
The right hand column places Adobe Lightroom Classic by scope and by the sort of operator it serves, with no attempt at a priced feature list. Both keep changing, so check the current shape of each one before you choose. PaperKeepsake is published by MLJ, SASU and this page is written by Jimenez Julien.
A catalog answers a question about images: where is the frame, what does it look like, how has it been adjusted. A photo organizing project raises different questions entirely. Which box did this print come out of. Has that box gone back to the client yet. Did batch 14 get rescanned after the roller mark showed up. How many images are still waiting on a date. Is the aunt in the 1961 beach photos the same aunt in the 1978 graduation photos.
Lightroom Classic can be bent toward some of that with collections and keyword hierarchies, and experienced organizers have done it for years. The bending is the cost. Every studio that does it builds a private convention that nobody else on the team learns quickly, and it usually lives in one catalog file on one machine. PaperKeepsake starts from the project shape instead, so the box, the batch and the family are first class rather than improvised.
The hardest metadata in a family archive is the part nobody wrote down. A shoebox of 1970s drugstore prints often has a processing date on the back, sometimes a month, frequently nothing at all. Slides may carry a stamp on the mount. Album pages carry a sequence but no year. Working archives need a way to say 1958 to 1963 and mean it, and to keep that range distinct from a date somebody actually confirmed.
PaperKeepsake treats a circa range as a legitimate value and keeps confirmed dates separate from estimated ones, so a family can later see which is which. Unknown people work the same way. A face can be tracked across hundreds of images before anyone puts a name to it, and when the client's cousin finally identifies her, the name lands everywhere at once. A photographer's catalog has less reason to model any of this, because a camera already answered the date question.
The common arrangement in working studios is a clean split. Capture and correction happen where they already happen, whether that is Lightroom Classic, your scanner software, or a copy stand tethered to a laptop. The corrected files then belong to a project in PaperKeepsake, where batch counts, dates, names and delivery status live, and where the family index is assembled.
The one rule that keeps this honest is writing metadata into the files themselves rather than leaving it only in an app. Names and dates embedded in IPTC and EXIF fields travel with the images when a family moves them to a hard drive, a cloud service, or whatever replaces both in fifteen years. That is the deliverable your client is really paying for, and it should never be trapped in one vendor's database, including ours.
Yes, and that is the usual setup. Correct the images wherever you correct them now, then work the project record, tagging and family index in PaperKeepsake. The two do not compete for the same task.
No. It does not straighten, crop, remove dust or fix a color shift on a faded print. Those belong in your capture and correction software, and we would rather do one job well than a second job badly.
PaperKeepsake, because a catalog has no idea a physical box exists. Boxes, batch numbers and return status are part of the project record, so you can answer a client's Monday morning phone call without hunting through a spreadsheet.
Comparison
Mylio Photos is a library that lives with the family across their own devices, and PaperKeepsake is the studio side record of the work that fills a library like that.
Comparison
Dubsado is a client management suite for service businesses, and PaperKeepsake is the record of the archive work itself, from box intake to the family index.
Reading two columns is not the same as running one engagement through both. In a demo we take a project of yours, load the box counts and batch numbers, and show you where the record comes out cleaner and where it does not. Half an hour, and nothing has to move off your capture station.