A mutation certificate is not the land as it sits today. It is the revenue paper that says the books moved: who left the occupancy, who arrived, on what instrument, under which order. In Maharashtra the masthead often says फेरफार, ferfar — Village Form VI, one numbered entry in the mutation register. A bank, a buyer’s lawyer, a tahsildar window will ask for a photocopy of that entry. You can scan mutation certificate to PDF on phone in a minute and still fail the ask, because the file is a photograph of a Marathi ledger named IMG_4471, not a ferfar mutation photocopy searchable by mutation number, outgoing occupant, or the deed they told you to match.

This is not a guide to filing ferfar, objecting on Aapli Chawadi, or whether a pending entry will certify. It is how to turn the certified extract already in the file into one named, searchable PDF. On the device. Not in a shop. Not in a cloud scanner.

Why a ferfar mutation photocopy has to be searchable

They want the change: mutation number, village and survey, outgoing occupant, incoming occupant, nature of the entry — sale, inheritance, gift, partition, decree — the date of the order, the shera that says it is final. Not a selfie of today’s village extract. Not a crop of one name. A copy of the mutation, as if a xerox machine had seen the register.

Form VI is unkind to a shop xerox. Eight-point ferfar numbers sit against shares in fractions. Marathi remarks pack against a deed reference. A 3 in the mutation number becomes an 8. The word वारस — inheritance — washes into the neighbouring sale. The शेरा a lender is hunting — certified, pending, under objection — smudges into the talathi’s stamp.

A camera-roll JPEG fails more quietly. The ferfar number is in the picture. It is not in the file. Search the phone for फेरफार, or the village, or the incoming occupant as the register spelled them, and nothing comes back. A loan pack opens on Friday. You scroll Recents.

A ferfar mutation photocopy searchable as a PDF is a different object. The sheet sits square. The file has a name. Optical character recognition writes the mutation number, both occupants, the nature of the change, and the order date into an invisible text layer. A JPEG of the remarks column cannot answer “was this ferfar certified.” A text layer can.

This is the change. Not the 7/12. Not the deed. Not the khata. Not the EC.

The 7/12 extract is who occupies the survey now, and last season’s crop. Mutation numbers printed on that sheet point at Form VI. They are not Form VI. Scanning today’s saat bara and labelling the file ferfar is a rumour of a change.

The sale deed is how land moved at the sub-registrar. Mutation is how the revenue village noticed. Banks often want both, as two files. Do not bind the registered instrument into the ferfar.

A khata extract is a municipal account of an urban plot. Some city desks say “mutation” and mean a name change on that tax account. That paper is not Village Form VI. If they asked for ferfar, send ferfar.

An encumbrance certificate searches Book 1 at the SRO. Mutation is the revenue register, not the registration index. A clean EC does not prove the talathi certified the name.

An 8A lists every holding one person has in the village. A legal heir certificate is often the reason a varas ferfar was entered. Neither is the ferfar. Do not staple them in.

Pending is not certified. An application acknowledgement, an Aapli Chawadi screenshot, a WhatsApp of “फेरफार दाखल झाला,” is not the mutation certificate. Scan the issued extract — the entry whose शेरा reads final, or the digitally signed e-Ferfar.

Maharashtra’s MahaBhumi will regenerate an e-Ferfar if the village is on the electronic register: district, taluka, village, mutation number, then a PDF with a digital signature and a QR. Keep that file. A branch that still says “xerox of ferfar” often wants the face of the printed extract — Form VI columns, both names, the stamp. Keep both when you have both.

फेरफार, ferfar, pherphar, mutation extract, Village Form VI, namantaran — same revenue change, different spelling on the masthead. If the paper lists an outgoing occupant, an incoming occupant, and a mutation number, that is the change. Scan it as issued.

What the photocopy has to keep

Open the PDF before the paper goes back in the sleeve:

  • Village, taluka, district. A neighbouring village with the same survey is a different holding
  • Mutation / ferfar number in full. An 8 that might be 0 is a rejected pack
  • Survey or gat number, including the hissa if the entry carries one
  • Outgoing occupant as recorded — the revenue spelling, not the spelling on the deed
  • Incoming occupant, including shares. Crop the last name in a varas list and you photocopied a different family
  • Nature of the mutation: sale, gift, partition, court decree, वारस
  • Deed, court, or heir reference if the remarks column names one
  • Date of entry and date of certification. A pending row is not a certified mutation
  • Shera / remarks in full — final, objection, stay
  • Officer and stamp: talathi who entered, circle officer or tahsildar who certified
  • QR or digital signature on an e-Ferfar print
  • Reverse, if an endorsement or a continuation of heirs lives there

If any of that is a crease through the ferfar number, glare on the QR, or Marathi remarks lost to a shadow, reshoot while the original is still on the table.

Old Form VI is thin; the handwritten registers are worse — faded ink, a bind edge that eats the number, shera in a running hand. Slide a dark sheet underneath — scanning thin paper without bleed-through is backing, not a brighter lamp. Flatten folds first. Do not iron it. Do not peel the sleeve.

A JPEG is not the photocopy they asked for. PDF versus photo is the same fork: a file you can attach to a loan portal and find two sales later, not a thumbnail that dies in a chat backup. One mutation number, one file. Do not bind the Baramati sale ferfar to the Nashik varas because both say mutation.

How to scan mutation certificate to PDF on phone

Treat the phone as the xerox machine. One certified entry, one PDF.

  1. Separate this sheet from the pile. The current 7/12, the deed, the 8A, and the heir list are not this file.
  2. Unclip. Flatten. A fold through the ferfar number is a change you will argue about.
  3. Dark, matte table. Tinted paper loses its edge on a white counter.
  4. Side light, never the flash. Tilt until glare leaves the mutation number, both occupant blocks, and the QR.
  5. All four corners. Landscape tables stay landscape; do not pinch Form VI into a portrait crop that eats the shera.
  6. Front, then reverse, then every continuation page. Handwritten pre-digital registers often run onto the facing leaf — capture that leaf too.
  7. Export PDF, not JPEG. A photo is a picture of a ledger. A PDF is the mutation photocopy.
  8. Name it without the ferfar number. Ferfar-Baramati-village.pdf is a document. Mutation-4471.pdf parks a register number in every folder listing. Let search find the number inside the file.
  9. Read the mutation number, both occupants, and the nature of the change out loud. Then search the phone for फेरफार, or the village, or mutation. Silence means the text layer is missing — a picture, not a ferfar mutation photocopy searchable later.

That last look is the difference. Scan mutation certificate to PDF on phone and you have a file. A camera-roll JPEG is a rumour of a change.

Extracts are Marathi first. Devanagari sits in the same block as the English — फेरफार, गाव नमुना ६, कब्जेदार, शेरा, वारस नोंद. Hindi-belt namantaran sheets do the same in another script. On-device OCR that reads those scripts is what makes the ferfar mutation photocopy searchable. Scanning Hindi and Tamil documents is the same craft, pointed at a mutation register instead of a letter.

On-device, no cloud, because a mutation maps who left and who arrived

A mutation certificate carries a village, a survey, a name that used to occupy, a name that occupies now, often a family list in a varas entry, often a registered deed number. Enough for a desk to believe the books moved. Enough for a stranger to map a transfer, an inheritance, a partition. Uploading it to a “free” scanner so the app can enhance the image is a bad trade. The shop xerox at least stays on paper you can shred. A cloud OCR copy lives on a machine you will never see.

Unlike a card you might mask before sharing, this photocopy is the change in words. Blacking out the outgoing occupant usually defeats the ask. If they asked for the mutation certificate, they asked for the register as issued. The protection is not redaction. It is leaving that holding off machines you do not run.

On-device capture and OCR keep the photocopy on the phone. Airplane mode is a blunt test: if you can still scan mutation certificate to PDF on phone with the radios off, the ferfar did not leave.

LumenScan is built for that file-drawer moment — flatten a bilingual ledger, on-device OCR so the ferfar mutation photocopy is searchable, files that stay on the device. Scanning documents without uploading them is the same rule, applied to a mutation entry instead of a letter.

Do not send the same PDF into five WhatsApp groups “just in case.” Chat apps compress eight-point ferfar numbers into mush and then lose the thread. One named file, one desk, done. If they asked for the mutation, send the mutation — not the 7/12 they did not name, and not the deed they did not name.

Keep the ferfar. Leave the register for the paper.

You do not need a new personality as a person who files talathi paper. You need the mutation number, both occupants, and the nature of the change to open when a counter asks, without a xerox run at the junction or a scroll through the camera roll.

Search the phone for फेरफार, or the village, or mutation. Silence means clutter, not a copy. Scan mutation certificate to PDF on phone once per certified entry, make the ferfar mutation photocopy searchable, and leave the IMG_ files out of the loan zip.

Want the photocopy, the OCR, and the file to stay on the device? Start with LumenScan on the App Store or Google Play — and read more on the Lumen Labs journal.